From: "Jiang Xin"
2015-08-02 21:42 GMT+08:00 Philip Oakley :
Separate out the three different contribution styles for existing,
new,
and wider mis-translation contributions, with suitable headings for
easy
reference.
In particular highlight the appropriate action should
From: "Jarkko Hietaniemi"
Thanks (also to Jacob Keller), the git-notes might work in some cases.
But it's obviously a pasted-on solution, requiring a different usage,
e.g. "git log --notes", and whatever other UIs do with it.
One more thing, if you know that no one has fetched the branch you
j
From: "Jiang Xin"
2015-08-04 6:29 GMT+08:00 Philip Oakley :
Hi Jiang,
This is my updated patch based on your feedback at $gmane/275141
and $gmane/275142.
I've used most of your wording, though have retained a comment on
considering if the translation could be held her
From: "Jiang Xin"
From: Philip Oakley
Some Linux distributions (such as Ubuntu) have their own l10n
workflows,
and their translations may be different. Add notes for this case for
l10n translators.
Signed-off-by: Philip Oakley
Signed-off-by: Jiang Xin
---
po/R
From: "Jacob Keller"
On Wed, Aug 26, 2015 at 10:56 AM, Junio C Hamano
wrote:
But notice that I said "if you really want to". I personally think
it is a road to madness.
Agreed. I don't believe in command line API here. I think we'd need a
better solution.
My gut says: Live with the warts o
From: "Alex Henrie"
Signed-off-by: Alex Henrie
---
builtin/show-ref.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/show-ref.c b/builtin/show-ref.c
index dfbc314..131ef28 100644
--- a/builtin/show-ref.c
+++ b/builtin/show-ref.c
@@ -8,7 +8,7 @@
static const char * c
From: "Jacob Keller"
On Thu, Sep 10, 2015 at 11:44 AM, Junio C Hamano
wrote:
Jacob Keller writes:
I hadn't thought of separating the cover letter from git-send-email.
That would be suitable for me.
Yeah, I said this number of times over time, and I said it once
recently in another thread,
From: "Johannes Schindelin"
On 2015-09-10 23:00, Jacob Keller wrote:
On Thu, Sep 10, 2015 at 11:58 AM, Johannes Schindelin
wrote:
On 2015-09-10 18:28, Jacob Keller wrote:
does anyone know of any tricks for storing a cover letter for a
patch
series inside of git somehow?
It is not stored
From: "Junio C Hamano"
Sent: Saturday, September 12, 2015 9:29 AM
Jeff King writes:
Yeah, I think what is happening in this first hunk:
...
is doing the right thing. It did feel a little weird to me to be
munging
the global commit objects themselves, but I guess it is fairly normal
for git
The branch description will be included in 'git format-patch
--cover-letter' and in 'git pull-request' emails. Tell the reader.
While here, clarify that the description may be a multi-line
explanation of the purpose of the branch's patch series.
Signed-off-by: Philip Oak
From: "Jacob Keller"
Hi,
On Sat, Sep 12, 2015 at 3:51 PM, Philip Oakley
wrote:
The branch description will be included in 'git format-patch
--cover-letter' and in 'git pull-request' emails. Tell the reader.
While here, clarify that the description may be a
From: "Philip Oakley"
From: "Jacob Keller"
Hi,
On Sat, Sep 12, 2015 at 3:51 PM, Philip Oakley
wrote:
The branch description will be included in 'git format-patch
--cover-letter' and in 'git pull-request' emails. Tell the reader.
[...]
Are these th
ranch's patch series.
Signed-off-by: Philip Oakley
---
fc0aa39 (Documentation: include 'merge.branchdesc' for merge
and config as well, 2015-05-27) recently added details of the
low level config flag.
Changes since V1: discovered that git merge can also include
the branch descrip
From: "Junio C Hamano"
Sent: Monday, September 14, 2015 11:43 PM
--
[New Topics]
* po/doc-branch-desc (2015-09-14) 1 commit
(merged to 'next' on 2015-09-14 at 4934a96)
+ doc: show usage of branch description
The branch descriptions that are
Oops..
From: "Philip Oakley"
[New Topics]
* po/doc-branch-desc (2015-09-14) 1 commit
(merged to 'next' on 2015-09-14 at 4934a96)
+ doc: show usage of branch description
The branch descriptions that are set with "git
branch --edit-description"
option wer
From: "Junio C Hamano"
"Philip Oakley" writes:
It still means that my patch is incomplete in its aim to bring out
these possible broader usages.
I haven't yet looked at the mail archives to see if there is more
around the time of those introductions.
I guess this
From: "Junio C Hamano"
"Philip Oakley" writes:
It still means that my patch is incomplete in its aim to bring out
these possible broader usages.
I haven't yet looked at the mail archives to see if there is more
around the time of those introductions.
I guess this
From: "Jacob Keller"
On Mon, Sep 28, 2015 at 1:42 PM, Junio C Hamano wrote:
"George Spelvin" writes:
I understand that "git reset --soft" makes no sense with a path, but
why not --hard?
I do not think there is anything fundamentally wrong for wishing for
"reset --hard ". It probably is ju
From: "Ed Avis"
Sent: Wednesday, June 03, 2015 10:55 AM
Jeff King peff.net> writes:
I would say the more "usual" way to use checkout like this
is to give specific paths. I.e., run "git status", say "oh, I need to
restore the contents of 'foo', but not 'bar'", and run "git checkout
foo". That
From: "Christian Couder"
Hi,
On Thu, Jun 4, 2015 at 3:04 PM, Rossella Barletta
wrote:
Dear git group,
I would like to ask your help for a problem that we cannot fix in any
way.
We have a git repository in folder on Windows.
Then we use VMware player on CentOS_6 on which we create a clon
uite.
Signed-off-by: Philip Oakley
---
.gitignore | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/.gitignore b/.gitignore
index 422c538..55498c1 100644
--- a/.gitignore
+++ b/.gitignore
@@ -246,5 +246,6 @@
*.user
*.idb
*.pdb
-/Debug/
-/Release/
+*.manifest
+**/Debug/
+*
Signed-off-by: Philip Oakley
---
contrib/buildsystems/engine.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/buildsystems/engine.pl b/contrib/buildsystems/engine.pl
index 23da787..5398315 100755
--- a/contrib/buildsystems/engine.pl
+++ b/contrib/buildsystems
.
Original author: Johannes Schindelin (2011-11-01 3142da4 : Add a script
to make the MSVC build more convenient).
Signed-off-by: Philip Oakley
---
TODO:
Also resolve the cleaning of newer VS2010 products.
---
compat/vcbuild/README | 2 +-
compat/vcbuild/scripts/msvc-
ee9be06 (perl: detect new files in MakeMaker builds, 2012-07-27)
did not include dry-run support for the generation of the PM.stamp
file, though the dry-run output is used by the build engine.
Disable the perl processing during the dry-run to avoid the issue.
Signed-off-by: Philip Oakley
same vein as
74cf9bd (engine.pl: Fix a recent breakage of the buildsystem
generator, 2010-01-22).
Signed-off-by: Philip Oakley
---
contrib/buildsystems/engine.pl | 6 ++
1 file changed, 6 insertions(+)
diff --git a/contrib/buildsystems/engine.pl b/contrib/buildsystems/engine.pl
index ccb59f
Signed-off-by: Philip Oakley
---
.gitignore | 3 +++
1 file changed, 3 insertions(+)
diff --git a/.gitignore b/.gitignore
index 55498c1..706d0d9 100644
--- a/.gitignore
+++ b/.gitignore
@@ -177,6 +177,7 @@
/gitweb/gitweb.cgi
/gitweb/static/gitweb.js
/gitweb/static/gitweb.min.*
+/libgit
The engine.pl script barfs on the properly quoted spaces in
filename options prevalent on Windows. Use shellwords() rather
than split() to separate such options.
Helped-by: Junio C Hamano
Signed-off-by: Philip Oakley
---
$gamane/21145 & $gmane/21147
---
contrib/buildsystems/engine.pl
Delete the duplicated GUID from the generation code for the Visual Studio
.sln project file.
The duplicate GUID tended to be allocated to test-svn-fe, which was then
ignored by Visual Studio / MSVC, and it's omission from the build never
noticed.
Signed-off-by: Philip Oakley
---
co
source .c filename.
Signed-off-by: Philip Oakley
---
contrib/buildsystems/engine.pl | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/contrib/buildsystems/engine.pl b/contrib/buildsystems/engine.pl
index 73f2472..e8aa8ea 100755
--- a/contrib/buildsystems/engin
Save the stderr from the dry MSVC make to a well named file for
later review. Use 'msvc-build-makedryerrors.txt' which should be
obvious as to its source, and is not ignored by 'git status'.
Signed-off-by: Philip Oakley
---
contrib/buildsystems/engine.pl | 5 -
1 file c
Add a debug suggestion for capturing to file the stdout from the dry-run
of the make file used in determining the msvc-build structure for easy
debugging.
Signed-off-by: Philip Oakley
---
contrib/buildsystems/engine.pl | 1 +
1 file changed, 1 insertion(+)
diff --git a/contrib/buildsystems
issue and the available
solutions of either NO_PERL or a '+recipe'.
Signed-off-by: Philip Oakley
---
Makefile | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Makefile b/Makefile
index 149f1c7..22108bb 100644
--- a/Makefile
+++ b/Makefile
@@ -1746,6 +1746,9 @@ $(SCRIPT_PERL_GEN): p
group of entries in the "GlobalSection(ProjectConfigurationPlatforms)
= postSolution" group that has the GUID of the project you moved to
the top. So there are two places to move lines."
Signed-off-by: Philip Oakley
---
contrib/buildsystems/Generators/Vcproj.pm | 33 +++
Signed-off-by: Philip Oakley
---
config.mak.uname | 9 +
1 file changed, 9 insertions(+)
diff --git a/config.mak.uname b/config.mak.uname
index 943c439..1c27828 100644
--- a/config.mak.uname
+++ b/config.mak.uname
@@ -1,5 +1,9 @@
# Platform specific Makefile tweaks based on uname
is doubly hard to get developers to ride both horses so, contrary to
normal convention, retain selected debug statements as a safety net for
those willing to try.
Signed-off-by: Philip Oakley
---
contrib/buildsystems/engine.pl | 4
1 file changed, 4 insertions(+)
diff --git a/contr
Layout the 'either/or' with more white space to clarify
which alternatives are matched up.
Reference the Msysgit build script which automates one sequence of options.
Signed-off-by: Philip Oakley
---
compat/vcbuild/README | 27 +++
1 file changed, 19 insert
jRshY
https://github.com/msysgit/git/pull/318/files
Hopefully it's not too late in the cycle for a review of this contrib/compat
item.
Philip Oakley (17):
.gitignore: improve MSVC ignore patterns
.gitignore: ignore library directories created by MSVC VS2008
buildsystem
(msvc-build)
file. They
are omitted if the release is tagged and indentically defined in
their respective GIT_VERSION_GEN file DEF_VER variables.
Signed-off-by: Philip Oakley
---
contrib/buildsystems/engine.pl | 2 ++
1 file changed, 2 insertions(+)
diff --git a/contrib/buildsystems/engine.pl b/contrib
From: "Junio C Hamano"
Philip Oakley writes:
Hopefully it's not too late in the cycle for a review of this
contrib/compat
item.
Has this been discussed in the Windows land and folks are all happy
with this change? If so the only thing we would need review on the
main
From: "Junio C Hamano"
Philip Oakley writes:
Add the Microsoft .manifest pattern, and correct the generic 'Debug'
and 'Release' directory patterns which were mechanically adjusted way
back in c591d5f (gitignore: root most patterns at the top-level
director
From: "Junio C Hamano"
Philip Oakley writes:
A 'make -n' dry-run is used as part of the /compat/vcbuild and
/contrib/buildsystems code. The commit ee9be06 (perl: detect new
files
in MakeMaker builds, 2012-07-27) was not aware of that dry-run usage
and thus would no
From: "Junio C Hamano"
"Philip Oakley" writes:
From: "Junio C Hamano"
I am not sure what this patch is trying to achieve.
It was probably a bit of 'don't mess with working code', given that
I'd used the NO_PERL solution, rather 'do
From: "Eric Sunshine"
On Wed, Jun 24, 2015 at 8:03 PM, Philip Oakley
wrote:
Delete the duplicated GUID from the generation code for the Visual
Studio
.sln project file.
The duplicate GUID tended to be allocated to test-svn-fe, which was
then
ignored by Visual Studio / MSVC
From: "Sebastian Schuberth"
On 25.06.2015 02:03, Philip Oakley wrote:
--- a/contrib/buildsystems/engine.pl
+++ b/contrib/buildsystems/engine.pl
@@ -41,6 +41,7 @@ EOM
# Parse command-line options
while (@ARGV) {
my $arg = shift @ARGV;
+ #print "Arg: $arg \n";
From: "David Turner"
The current state of the discussion on alternate ref backends is that
we're going to continue to store pseudorefs (e.g. CHERRY_PICK_HEAD) as
Assuming this is accepted, should the definition of pseudorefs be
included in the gitglossary?
Once ref backends become common, t
From: Sent: Sunday, July 12, 2015 10:39 AM
From: Ilya Bobyr
It is not very likely that any of the "*=?!" Characters would be
useful
in the argument short or long names. On the other hand, there are
already argument hints that contain the "=" sign. It used to be
impossible to include any of
uld be redundant.
I have also made a slight addition to the man page to clarify the
parsing, based on the Philip Oakley comment. Not sure if it is at the
level Philip wants it to be. Please, let me know if you think it is
still
not good enough.
The doc patch looks good. I've made
It looks like Git has a healthy truck factor of 8, as reported in
https://mtov.github.io/Truck-Factor/, which has Git eighth in the list
of projects it analyzed, with Linux at second place.
The analysis method paper is behind a pay wall, so I couldn't see how
sensible the methodology, but it's
From: "Philip Oakley"
Sent: Friday, June 26, 2015 12:34 AM
From: "Junio C Hamano"
"Philip Oakley" writes:
From: "Junio C Hamano"
I am not sure what this patch is trying to achieve.
I have been able to repeat the issue, more below.
It was pr
From: "Junio C Hamano"
As the nature of the conflict marker line determies if there should
"should be a"?
i.e. s/a /be a /below
a SP and label after it, the caller shouldn't have to pass the
parameter redundantly.
Signed-off-by: Junio C Hamano
---
rerere.c | 27 ++--
it msvc-build
script which implements the compat/vcbuild/README using
contrib/buildsystems. The script msvc-build is introduced later in this
series.
Protect the PM.stamp target when the PM.stamp file does not exist,
allowing a Git 'Makefile -n' to succeed on a clean repo.
Signed-off-
Signed-off-by: Philip Oakley
---
contrib/buildsystems/engine.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/buildsystems/engine.pl b/contrib/buildsystems/engine.pl
index 23da787..c8a5258 100755
--- a/contrib/buildsystems/engine.pl
+++ b/contrib/buildsystems
Add a debug suggestion for capturing to file the stdout from the dry-run
of the make file used in determining the msvc-build structure for easy
debugging.
Signed-off-by: Philip Oakley
---
contrib/buildsystems/engine.pl | 1 +
1 file changed, 1 insertion(+)
diff --git a/contrib/buildsystems
Signed-off-by: Philip Oakley
---
.gitignore | 3 +++
1 file changed, 3 insertions(+)
diff --git a/.gitignore b/.gitignore
index 91e75ee..e35c492 100644
--- a/.gitignore
+++ b/.gitignore
@@ -178,6 +178,7 @@
/gitweb/gitweb.cgi
/gitweb/static/gitweb.js
/gitweb/static/gitweb.min.*
+/libgit
Delete the duplicated GUID from the generation code for the Visual Studio
.sln project file.
The duplicate GUID tended to be allocated to test-svn-fe, which was then
ignored by Visual Studio / MSVC, and its omission from the build never
noticed.
Signed-off-by: Philip Oakley
---
Eric Sunshine
gle.com/forum/?hl=en_US?hl%3Den#!topic/msysgit/aiEVBKjRshY
and as a PR https://github.com/msysgit/git/pull/318/files
Philip Oakley (16):
perl/Makefile: treat a missing PM.stamp as if empty
.gitignore: improve MSVC ignore patterns
.gitignore: ignore library directories created by MSVC VS2008
e GUID of the project you moved to
the top. So there are two places to move lines."
Signed-off-by: Philip Oakley
---
contrib/buildsystems/Generators/Vcproj.pm | 33 ++-
1 file changed, 19 insertions(+), 14 deletions(-)
diff --git a/contrib/buildsystems/
Layout the 'either/or' with more white space to clarify
which alternatives are matched up.
Reference the Msysgit build script which automates one sequence of options.
Signed-off-by: Philip Oakley
---
compat/vcbuild/README | 27 +++
1 file changed, 19 insert
ff-by: Philip Oakley
---
Junio/my discussion on reviews: http://marc.info/?l=git&m=143526063906215&w=2
(2015-06-25)
Patch series v1: https://github.com/msysgit/git/pull/318
Yue Lin Ho: https://github.com/msysgit/git/pull/318#issuecomment-81292918
---
config.mak.uname | 9 +
1 fi
source .c filename.
Signed-off-by: Philip Oakley
---
contrib/buildsystems/engine.pl | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/contrib/buildsystems/engine.pl b/contrib/buildsystems/engine.pl
index 60c7a7d..9db3d43 100755
--- a/contrib/buildsystems/engin
Save the stderr from the dry MSVC make to a well named file for
later review. Use 'msvc-build-makedryerrors.txt' which should be
obvious as to its source, and is not ignored by 'git status'.
Signed-off-by: Philip Oakley
---
fixed false mode change:- Junio's report (last
file. They
are omitted if the release is tagged and indentically defined in
their respective GIT_VERSION_GEN file DEF_VER variables.
Signed-off-by: Philip Oakley
---
contrib/buildsystems/engine.pl | 2 ++
1 file changed, 2 insertions(+)
diff --git a/contrib/buildsystems/engine.pl b/contrib
same vein as
74cf9bd (engine.pl: Fix a recent breakage of the buildsystem
generator, 2010-01-22).
Signed-off-by: Philip Oakley
---
contrib/buildsystems/engine.pl | 6 ++
1 file changed, 6 insertions(+)
diff --git a/contrib/buildsystems/engine.pl b/contrib/buildsystems/engine.pl
index 24b899
part of final binary code) and it will be having
traceability to its low level requirements (its a intentional code and
it can be activated in some configurations through hardware traps for
debugging or other purposes.
Signed-off-by: Philip Oakley
---
My response to Sebastian Schuberth's co
The engine.pl script barfs on the properly quoted spaces in
filename options prevalent on Windows. Use shellwords() rather
than split() to separate such options.
Helped-by: Junio C Hamano
Signed-off-by: Philip Oakley
---
Junio's help at gmane.comp.version-control.msysgit/21145 (2014-
uite.
Signed-off-by: Philip Oakley
---
Junio's correction http://marc.info/?l=git&m=143524522500906&w=2
(2015-06-25)
---
.gitignore | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/.gitignore b/.gitignore
index a685ec1..91e75ee 100644
--- a/.gitignore
+++ b/.giti
ectories.
The script is made executable in line with $msysgit/cb9836b8a
(Mark scripts and binaries in /bin/ as executable, 2012-06-26)
Signed-off-by: Philip Oakley
---
TODO:
resolve any further cleaning of newer VS2010... build products.
---
compat/vcbuild/README | 2 +
compat/vcbuil
Layout the 'either/or' with more white space to clarify
which alternatives are matched up.
A revised copy of the Msysgit msvc-build script which automates this
README is introduced in the next commit.
Signed-off-by: Philip Oakley
---
compat/vcbuild/README | 25 +--
From: "Philip Oakley"
Sent: Sunday, July 19, 2015 9:08 PM
This "14/16" is the wrong version accidently left over from a previous
draft.
Please use the other version with the shorter subject line.
Sorry for the noise / mistake.
Layout the 'either/or' with mor
I've been using git-send-email with repeated individual --cc="email
address" parameters on the command line.
I tried putting all the addresses, one per line, into a file 'cc-cmd',
so I could use if for the --cc-cmd option.
I then tried to use --cc-cmd='cat cc-cmd' to do the send-email (as
a
From: "Eric Sunshine"
On Sun, Jul 19, 2015 at 6:02 PM, Philip Oakley
wrote:
I've been using git-send-email with repeated individual --cc="email
address"
parameters on the command line.
I tried putting all the addresses, one per line, into a file
'cc-cmd
From: "Eric Sunshine" Sent: Monday, July 20,
2015 2:54 AM
On Sun, Jul 19, 2015 at 4:08 PM, Philip Oakley
wrote:
Commit 4b623d8 (MSVC: link in invalidcontinue.obj for better
POSIX compatibility, 2014-03-29) is not processed correctly
by the buildsystem. Ignore it.
What does &quo
From: "Eric Sunshine"
On Sun, Jul 19, 2015 at 4:08 PM, Philip Oakley
wrote:
Keep the build clean of extraneous files if it is indeed clean.
Otherwise leave the msvc-build-makedryerrors.txt file both as
a flag for any CI system or for manual debugging.
Note that the file will conta
From: "Eric Sunshine"
On Mon, Jul 20, 2015 at 2:16 AM, Philip Oakley
wrote:
From: "Eric Sunshine"
On Sun, Jul 19, 2015 at 4:08 PM, Philip Oakley
wrote:
Keep the build clean of extraneous files if it is indeed clean.
Otherwise leave the msvc-build-makedryerrors.txt fil
From: "Eric Sunshine"
On Mon, Jul 20, 2015 at 2:01 AM, Philip Oakley
wrote:
From: "Eric Sunshine"
git-send-email invokes the cc-cmd like this:
$cc-cmd $patchfilename
so, when you used 'cat cc-cmd' as the value of --cc-cmd, your
invocation
became:
Explain how the cc-cmd (and to-cmd) is invoked, along with two
simple examples (and a how-not-to example) to help in getting started.
Helped-by: Eric Sunshine
Signed-off-by: Philip Oakley
---
http://article.gmane.org/gmane.comp.version-control.git/274302
---
Documentation/git-send-email.txt
n docbook'ed.
The series could be squashed together..
Philip Oakley (3):
doc: convert send-email option headings to nouns
doc: send-email; expand on the meaning of 'auto-cc'
doc: give examples for send-email cc-cmd operation
Documentation/git-send-email.txt | 54
Signed-off-by: Philip Oakley
---
Documentation/git-send-email.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
index bc357b8..ddc8a11 100644
--- a/Documentation/git-send-email.txt
+++ b/Documentation/git
Signed-off-by: Philip Oakley
---
Documentation/git-send-email.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
index bc357b8..ddc8a11 100644
--- a/Documentation/git-send-email.txt
+++ b/Documentation/git
... for ease of reference within the text.
Except the 'Sending options' for which there wasn't an
obvious noun phrase.
Signed-off-by: Philip Oakley
---
Documentation/git-send-email.txt | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/Documen
Sorry for the noise.
- Original Message -
From: "Philip Oakley"
To: "Git List"
Cc: "Junio C Hamano" ; "Eric Sunshine"
Sent: Monday, July 20, 2015 7:26 PM
Subject: [PATCH 2/3] doc: send-email; expand oon the meaning of
'auto-cc'
--
From: "Eric Sunshine"
On Mon, Jul 20, 2015 at 2:26 PM, Philip Oakley
wrote:
Explain how the cc-cmd (and to-cmd) is invoked, along with two
simple examples (and a how-not-to example) to help in getting
started.
Helped-by: Eric Sunshine
Signed-off-by: Philip Oakley
---
di
From: "Junio C Hamano"
Philip Oakley writes:
+git-send-email invokes the cc-cmd like this:
+
+ $cc-cmd $patchfilename
+
+Thus the patch itself can be processed to locate appropriate email
address
+information if required.
That's not even a valid command line (cc-cmd ca
This updates two patches in the series based on Eric Sunshine's comments.
Patch 8b updates the commit message to make clear what was going wrong.
Patch 10b improves the perl code.
Junio: would a full re-roll be appropriate at a suitable point?
Philip Oakley (2):
engine.pl: i
identically defined in
their respective GIT_VERSION_GEN file DEF_VER variables.
[1]: http://perldoc.perl.org/functions/-X.html
[2]: http://git-for-windows.github.io/
Helped-by: Eric Sunshine
Signed-off-by: Philip Oakley
---
Eric's help gmane.comp.version-control.msysgit/21745
---
contrib/buildsy
without source files)
separate.
Signed-off-by: Philip Oakley
---
contrib/buildsystems/engine.pl | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/contrib/buildsystems/engine.pl b/contrib/buildsystems/engine.pl
index 60c7a7d..9db3d43 100755
--- a/contrib/buildsystems/e
From: "Junio C Hamano"
Philip Oakley writes:
This updates two patches in the series based on Eric Sunshine's
comments.
Patch 8b updates the commit message to make clear what was going
wrong.
Patch 10b improves the perl code.
Is v2b like saying v3 or something else? Does 8
From: "Junio C Hamano"
Junio C Hamano writes:
"Philip Oakley" writes:
... Ideally, if part of this
mainstream Git, it would get picked up automatically by them
(rather than being local 'fixes' endlessly carried forward).
Actually, that is not "ideal&q
From: "Junio C Hamano"
Junio C Hamano writes:
I was trying to use, essentially, 'cat list.txt' as the command,...
One thing that needs to be made clear is that I do not think we want
to encourage `cat list.txt #` abuse in the first place.
OK [1]
It is an
unacceptable hack for us to en
From: "David Turner"
Add glossary entries for both concepts.
Pseudorefs and per-worktree refs do not yet have special handling,
because the files refs backend already handles them correctly. Later,
we will make the LMDB backend call out to the files backend to handle
per-worktree refs.
Signed
(In-line posting preferred; top-posting deprecated ;-)
(retain all cc's)
Hmm, it is already happening, isn't it? There is already a support of
MSVCR in git's code base. I am referring to replacing that current
support of 'older' MSVCR in favor of the latest one, so to make the
git's code base
Hi,
From: "Dangling Pointer"
I searched in code and found instances of #ifdef _MSC_VER in
https://github.com/git/git (original repository, not the fork).
I am coming from github, where I have found many native lib
repositories have two build files, build.sh and build.cmd with
Git is a *nix co
From: "Ovatta Bianca"
I read in every comparison of git vs other version control systems,
that git does not record differences but takes "snapshots"
I was wondering what a "snapshot" is ? Does git store at every commit
the entire files which have been modified even if only a few bytes
were chang
Hi,
Is there a common name for the A..B range format (two dots) that would
complement the A...B (three dots) symmetric range format's name?
I was looking at the --left-right distinctions and noticed that the trail
back to the symmetric range description was rather thin (it's buried within
gi
From: "Junio C Hamano"
Jeff King writes:
On Wed, Jun 22, 2016 at 08:25:59AM +0100, Philip Oakley wrote:
Is there a common name for the A..B range format (two dots) that would
complement the A...B (three dots) symmetric range format's name?
I was looking at the --left-rig
>> On Wed, Jun 22, 2016 at 08:25:59AM +0100, Philip Oakley wrote:
>>
>>> Is there a common name for the A..B range format (two dots) that would
>>> complement the A...B (three dots) symmetric range format's name?
$gmane/297908
Here is a short two patch series
While there, also break out the other shorthand notations and
add a title for the revision range summary (which also appears
in git-rev-parse).
Signed-off-by: Philip Oakley
---
Documentation/revisions.txt | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a
Signed-off-by: Philip Oakley
---
Documentation/gitk.txt | 2 +-
Documentation/rev-list-options.txt | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/gitk.txt b/Documentation/gitk.txt
index 6ade002..6c3eb15 100644
--- a/Documentation/gitk.txt
+++ b
Signed-off-by: Philip Oakley
---
This is a quick follow on to the 'symmetric difference' documentation patches
http://thread.gmane.org/gmane.comp.version-control.git/297908/focus=298223
where I checked all the uses of 'left' to see if other terms had been used.
I noticed t
From: "Junio C Hamano"
"Philip Oakley" writes:
Yup, I think "range" is the commonly used word in discussions here.
When inventing A...B as a new thing in addition to A..B, we called
the former "symmetric difference", and what is implied by that is
the
1 - 100 of 1323 matches
Mail list logo
