From: Charles Bailey <hidden> Date: 2016-06-15 22:44:03
Make the behaviour of a top level make NO_MSGFMT=Yes consistent when
performing the subdirectory builds in gitk-git and git-gui.
Signed-off-by: Charles Bailey <redacted>
---
gitk-git/Makefile | 7 ++++++-
{git-gui => gitk-git}/po/.gitignore | 0
{git-gui => gitk-git}/po/po2msg.sh | 0
3 files changed, 6 insertions(+), 1 deletions(-)
copy {git-gui => gitk-git}/po/.gitignore (100%)
copy {git-gui => gitk-git}/po/po2msg.sh (100%)
diff --git a/git-gui/po/.gitignore b/gitk-git/po/.gitignoresimilarity index 100%copy from git-gui/po/.gitignorecopy to gitk-git/po/.gitignorediff --git a/git-gui/po/po2msg.sh b/gitk-git/po/po2msg.shsimilarity index 100%copy from git-gui/po/po2msg.shcopy to gitk-git/po/po2msg.sh
--
1.5.4.rc2.60.gb2e62
From: Johannes Schindelin <hidden> Date: 2016-06-15 22:44:03
Hi,
On Wed, 9 Jan 2008, Charles Bailey wrote:
Make the behaviour of a top level make NO_MSGFMT=Yes consistent when
performing the subdirectory builds in gitk-git and git-gui.
Signed-off-by: Charles Bailey <redacted>
---
gitk-git/Makefile | 7 ++++++-
{git-gui => gitk-git}/po/.gitignore | 0
{git-gui => gitk-git}/po/po2msg.sh | 0
3 files changed, 6 insertions(+), 1 deletions(-)
copy {git-gui => gitk-git}/po/.gitignore (100%)
copy {git-gui => gitk-git}/po/po2msg.sh (100%)
Since gitk and git-gui are separate projects (pulled at irregular
intervals into git.git), your patch looks sane, but would be better done
as a patch against gitk.git.
Ciao,
Dscho
From: Charles Bailey <hidden> Date: 2016-06-15 22:44:03
On Wed, Jan 09, 2008 at 01:40:46PM +0000, Johannes Schindelin wrote:
Hi,
On Wed, 9 Jan 2008, Charles Bailey wrote:
quoted
--- snip ---
Since gitk and git-gui are separate projects (pulled at irregular
intervals into git.git), your patch looks sane, but would be better done
as a patch against gitk.git.
Ciao,
Dscho
I'm sorry, I think I knew this once, but had forgotten. Of course, as
a patch against gitk, I think it gets quite verbose as the patch
includes a full copy of the po2msg.sh script.
Is there a simple way to generate a gitk.git patch from a git.git
clone, or do I need to clone a gitk repository from somewhere?
Perhaps I could just flag this as a reasonably important MacOS X
1.5.4-rc issue until I can sort out a more suitable patch?
Thanks,
Charles.
From: Johannes Schindelin <hidden> Date: 2016-06-15 22:44:03
Hi,
On Wed, 9 Jan 2008, Charles Bailey wrote:
On Wed, Jan 09, 2008 at 01:40:46PM +0000, Johannes Schindelin wrote:
quoted
On Wed, 9 Jan 2008, Charles Bailey wrote:
quoted
--- snip ---
Since gitk and git-gui are separate projects (pulled at irregular
intervals into git.git), your patch looks sane, but would be better
done as a patch against gitk.git.
I'm sorry, I think I knew this once, but had forgotten.
Oh, my critique was not meant as harsh as it was apparently received: for
reviewing purposes, your way was perfect, as it shows your intent better
than the technically correct patch.
All I'm saying is that you should send the (verbose) patch, too, possibly
referring to the smaller patch in the space between the three dashes and
the diffstat.
(I would also prefix this patch with "gitk:", instead of writing "of
gitk", so that people reading the log of git.git get a better idea what
this is about.)
Ciao,
Dscho