"W. Trevor King" writes:
> On Sat, Feb 23, 2013 at 01:21:59PM -0800, Junio C Hamano wrote:
>> "W. Trevor King" writes:
>>
>> > +This hook is called by 'git rebase' and can be used to prevent a
>> > +branch from getting rebased. The hook takes two parameters: the
>> > +upstream the series was f
Jeff King writes:
>> Oddly, you seemed to miss the one in connect.c (which my sparse does
>> detect).
>
> Ah, I saw why as soon as I finished off the rebase: that (NULL, 0) goes
> away in the very next patch,...
Yeah, I noticed that myself while replacing 15. The patch in the
message I am respo
Mike Gorchak writes:
> Hello,
>
>> Here is a small patch with QNX build improvements:
>>
>> 1) Rename tar.h to tar_git.h. Latest QNX versions have system tar.h
>> header according to
>> http://pubs.opengroup.org/onlinepubs/009696699/basedefs/tar.h.html ,
>> to avoid inclusion of another tar.h, or
David Aguilar writes:
> This is referring to "git the command", not "git the system",
> so it should not be changed according to the rule that was
> applied when many "git" strings were changed to "Git".
That sounds like a sensible objection.
> There are scripts, etc. in the wild that parse thi
Philip Oakley writes:
> diff --git a/common-guides.h b/common-guides.h
> new file mode 100644
> index 000..a8ad8d1
> --- /dev/null
> +++ b/common-guides.h
> @@ -0,0 +1,12 @@
> +/* Automatically generated by ./generate-guidelist.sh */
> +/* re-use struct cmdname_help in common-commands.h */
H
Jeff King writes:
> On Fri, Jan 11, 2013 at 10:43:39AM -0800, Hilco Wijbenga wrote:
> ...
> More seriously, I agree that re-wording the question is a reasonable
> thing to do. I do not use send-email, either, so I don't have a strong
> opinion on it. The suggestions you made:
>
>> How about "What
Nguyễn Thái Ngọc Duy writes:
> Patterns in .gitattributes are separated by whitespaces, which makes
> it impossible to specify exact spaces in the pattern. '?' can be used
> as a workaround, but it matches other characters too. This patch makes
> a space following a backslash part of the pattern
Antoine Pelisse writes:
> When considering a rename for two files that have a suffix and a prefix
> that can overlap, a confusing line is shown. As an example, renaming
> "a/b/b/c" to "a/b/c" shows "a/b/{ => }/b/c".
This would be vastly more readable if it had "It should show XXX
instead" somewh
Hi,
Am 23.02.2013 21:42, schrieb Jonathan Nieder:
> diger wrote:
>
>> This patch fixes build git on Haiku
>
> Lovely. May we have your sign-off? (See
> Documentation/SubmittingPatches for what this means.) Does "make
> test" pass? (Just curious --- it's fine if it doesn't, though in that
> c
>>> 2) Rename fnmatch.h to fnmatch_gnu.h and fnmatch.c to fnmatch_gnu.c to
>>> avoid inclusion of system fnmatch.h header in case if -I/usr/include
>>> path is specified before -Icompat/fnmatch. Which is common situation.
> As to the substance, I am fairly negative about the approach this
> patch t
On Sat, Feb 23, 2013 at 11:05:50PM +, Philip Oakley wrote:
> +"Examples: 'git help git', 'git help branch', 'git help
> tutorial'..");
This sentence should end in '.', not '..'.
Cheers,
Trevor
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more info
On Sat, Feb 23, 2013 at 11:05:54PM +, Philip Oakley wrote:
> +# Usage: ./generate-guidelist.sh >>common-guides.h
Following David's recent series, it's probably better to use a
lowercase 'usage' [1]. Also, I'd expect '>common-guides.h' would make
more sense than appending with '>>'.
> +/* re
On Sat, Feb 23, 2013 at 11:05:57PM +, Philip Oakley wrote:
> diff --git a/Documentation/everyday.txt b/Documentation/everyday.txt
> index e1fba85..3fc69f6 100644
> --- a/Documentation/everyday.txt
> +++ b/Documentation/everyday.txt
> @@ -1,413 +1,25 @@
> -Everyday Git With 20 Commands Or So
> +
On Sat, Feb 23, 2013 at 11:06:00PM +, Philip Oakley wrote:
> OBSOLETE_HTML = git-remote-helpers.html
> +OBSOLETE_HTML = everyday.html
> +OBSOLETE_HTML = user-manual.html
> DOC_HTML=$(MAN_HTML) $(OBSOLETE_HTML)
Should be '+=' instead of '='.
--
This email may be signed or encrypted with Gnu
On Sat, Feb 23, 2013 at 11:06:01PM +, Philip Oakley wrote:
> diff --git a/Documentation/gituser-manual.txt
> b/Documentation/gituser-manual.txt
> index a4778d7..e991b11 100644
> --- a/Documentation/gituser-manual.txt
> +++ b/Documentation/gituser-manual.txt
> @@ -1,7 +1,12 @@
> Git User's Man
Yuri Mikhailov:
> Dear Git community,
>
> I am a Software Developer and I have been using git for a while.
> Currently my company is looking for a version control system to use
> and we find Git a good candidate for us. But what is important for us
> to know is scalability of this VCS. Does anyone
Hello,
There seems to be a security issue in the way git uses openssl for
certificate validation. Similar occurrences have been found and
documented in other open source projects, the research can be found at
[1].
-=]
- imap-send.c
Line 307
307 ret = SSL_connect(sock->ssl);
308 if
In 2012 there was a thread about git's performance on large
repositories. One archive of the discussion begins here:
http://mid.gmane.org/CB5074CF.3AD7A%25joshua.redstone%40fb.com
> The test repo has 4 million commits, linear history and about 1.3
> million files.
I'm not sure to what extent git
Fix git compilation without available libiconv library.
From: Mike Gorchak
Signed-off-by: Mike Gorchak
---
configure.ac | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index 1991258..d0e82c1 100644
--- a/configure.ac
+++ b/configure.ac
@@ -566,
On 02/24/2013 06:31 PM, Zubin Mithra wrote:
> Hello,
>
> There seems to be a security issue in the way git uses openssl for
> certificate validation. Similar occurrences have been found and
> documented in other open source projects, the research can be found at
> [1].
>
> -=]
> - imap-se
This matches the use of the variables with the same names in autotools,
reducing the potential for user surprise.
Using relative paths in these variables also causes issues if they are
exported from the Makefile, as discussed in commit c09d62f (Makefile: do
not export mandir/htmldir/infodir, 2013-
On Sun, Feb 24, 2013 at 8:58 AM, Thomas Koch wrote:
> Yuri Mikhailov:
>> Dear Git community,
>>
>> I am a Software Developer and I have been using git for a while.
>> Currently my company is looking for a version control system to use
>> and we find Git a good candidate for us. But what is importa
Mike Gorchak writes:
> CFLAGS="-I/usr/qnxVVV/include" LDFLAGS="-I/usr/qnxVVV/lib" ./configure
> --prefix=/usr
Oh, I didn't notice that, but the definition of ALL_CFLAGS may be
what is wrong. It allows CFLAGS to come before BASIC_CFLAGS that
adds -Icompat/, which goes against the whole point of
Thanks.
After applying these patches, "git grep '^[^#]*Usage:'" still shows
a handful more hits, such as contrib/examples/git-remote.perl that
are touched by this series.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More m
From: "Junio C Hamano"
Sent: Sunday, February 24, 2013 8:59 AM
David Aguilar writes:
This is referring to "git the command", not "git the system",
so it should not be changed according to the rule that was
applied when many "git" strings were changed to "Git".
That sounds like a sensible ob
From: "Junio C Hamano"
Sent: Sunday, February 24, 2013 9:01 AM
Philip Oakley writes:
diff --git a/common-guides.h b/common-guides.h
new file mode 100644
index 000..a8ad8d1
--- /dev/null
+++ b/common-guides.h
@@ -0,0 +1,12 @@
+/* Automatically generated by ./generate-guidelist.sh */
+/* re
On 24/02/13 14:39, W. Trevor King wrote:
On Sat, Feb 23, 2013 at 11:05:50PM +, Philip Oakley wrote:
+ "Examples: 'git help git', 'git help branch', 'git help
tutorial'..");
This sentence should end in '.', not '..'.
Cheers,
Trevor
I should have used three as ellipsis ... to sug
On Sun, Feb 24, 2013 at 12:59 AM, Junio C Hamano wrote:
> David Aguilar writes:
>
>> This is referring to "git the command", not "git the system",
>> so it should not be changed according to the rule that was
>> applied when many "git" strings were changed to "Git".
>
> That sounds like a sensibl
Compare with git-instaweb which is replaced by as a small shell script which
informs the user that the functionality is not implemented.
I've only checked git-submodule, other commands may also have an undocumented
dependency on perl.
--
To unsubscribe from this list: send the line "unsubscribe gi
On 24/02/13 14:51, W. Trevor King wrote:
On Sat, Feb 23, 2013 at 11:05:54PM +, Philip Oakley wrote:
+# Usage: ./generate-guidelist.sh >>common-guides.h
Following David's recent series, it's probably better to use a
lowercase 'usage' [1].
I prefer the Initial capital version to suggest the
On 24/02/13 14:55, W. Trevor King wrote:
On Sat, Feb 23, 2013 at 11:05:57PM +, Philip Oakley wrote:
diff --git a/Documentation/everyday.txt b/Documentation/everyday.txt
index e1fba85..3fc69f6 100644
--- a/Documentation/everyday.txt
+++ b/Documentation/everyday.txt
@@ -1,413 +1,25 @@
-Everyda
On 24/02/13 14:58, W. Trevor King wrote:
On Sat, Feb 23, 2013 at 11:06:00PM +, Philip Oakley wrote:
OBSOLETE_HTML = git-remote-helpers.html
+OBSOLETE_HTML = everyday.html
+OBSOLETE_HTML = user-manual.html
DOC_HTML=$(MAN_HTML) $(OBSOLETE_HTML)
Should be '+=' instead of '='.
Well spott
On 24/02/13 15:01, W. Trevor King wrote:
On Sat, Feb 23, 2013 at 11:06:01PM +, Philip Oakley wrote:
diff --git a/Documentation/gituser-manual.txt b/Documentation/gituser-manual.txt
index a4778d7..e991b11 100644
--- a/Documentation/gituser-manual.txt
+++ b/Documentation/gituser-manual.txt
@@
On Sun, Feb 24, 2013 at 1:45 PM, Junio C Hamano wrote:
> Thanks.
>
> After applying these patches, "git grep '^[^#]*Usage:'" still shows
> a handful more hits, such as contrib/examples/git-remote.perl that
> are touched by this series.
Thanks, I'll take a look at these.
I stayed away from tests
Make the usage string consistent with Git.
Signed-off-by: David Aguilar
---
I'm not sure why this wasn't caught in my first round.
It should probably be squashed into the 02/16 from v2.
git-svn.perl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/git-svn.perl b/git-svn.p
Adjust test commands and test suites so that their
usage strings are consistent with Git.
Signed-off-by: David Aguilar
---
t/lib-git-svn.sh | 2 +-
t/t1509/prepare-chroot.sh | 2 +-
test-chmtime.c| 2 +-
test-delta.c | 2 +-
test-genrandom.c | 2 +-
5 f
Make the usage string consistent with Git.
Signed-off-by: David Aguilar
---
contrib/examples/git-remote.perl | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/contrib/examples/git-remote.perl b/contrib/examples/git-remote.perl
index b549a3c..d42df7b 100755
--- a/contrib
Make the usage string consistent with Git.
Signed-off-by: David Aguilar
---
contrib/mw-to-git/t/install-wiki.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/mw-to-git/t/install-wiki.sh
b/contrib/mw-to-git/t/install-wiki.sh
index c6d6fa3..70a53f6 100755
--- a/contr
Hi,
this is a series I have been working on and off. My plan is that it
might be part of a slightly bigger series also implementing on-demand
clone of submodules into the .git/modules folder if a submodule is
configured like that.
This is needed as preparation for the final goal of automatic
chec
This can be used to read configuration values directly from gits
database.
Signed-off-by: Heiko Voigt
---
.gitignore | 1 +
Makefile | 1 +
cache.h| 1 +
config.c | 119 ++---
t/t1300-repo-c
Change calculation of changed submodule paths to read revisions config.
We now read the submodule name for every changed submodule path in a
commit. We then use the submodules names for fetching instead of the
submodule paths.
We lazily read all configurations of changed submodule path into a cac
To make extending this logic later easier.
Signed-off-by: Heiko Voigt
---
submodule.c | 50 +++---
1 file changed, 27 insertions(+), 23 deletions(-)
diff --git a/submodule.c b/submodule.c
index b603000..a6fe16e 100644
--- a/submodule.c
+++ b/submodule
Hello,
On Mon, Feb 25, 2013 at 12:16 AM, Andreas Ericsson wrote:
> On 02/24/2013 06:31 PM, Zubin Mithra wrote:
>> Hello,
>>
>> There seems to be a security issue in the way git uses openssl for
>> certificate validation. Similar occurrences have been found and
>> documented in other open source p
On Sun, Feb 24, 2013 at 11:01:50PM +0530, Zubin Mithra wrote:
> There seems to be a security issue in the way git uses openssl for
> certificate validation. Similar occurrences have been found and
> documented in other open source projects, the research can be found at
> [1].
>
> -=]
> -
On Sun, Feb 24, 2013 at 07:46:51PM +0100, Andreas Ericsson wrote:
> The lack of certificate authority verification presents no attack vector
> for git imap-send. As such, it doesn't warrant a CVE. I'm sure you'll
> be credited with a "reported-by" line in the commit message if someone
> decides to
"Philip Oakley" writes:
> From: "Junio C Hamano"
> Sent: Sunday, February 24, 2013 9:01 AM
>> Philip Oakley writes:
>>
>>> diff --git a/common-guides.h b/common-guides.h
>>> new file mode 100644
>>> index 000..a8ad8d1
>>> --- /dev/null
>>> +++ b/common-guides.h
>>> @@ -0,0 +1,12 @@
>>> +/*
Philip Oakley writes:
> @@ -35,6 +37,8 @@ MAN_XML=$(patsubst %.txt,%.xml,$(MAN_TXT))
> MAN_HTML=$(patsubst %.txt,%.html,$(MAN_TXT))
>
> OBSOLETE_HTML = git-remote-helpers.html
> +OBSOLETE_HTML = everyday.html
> +OBSOLETE_HTML = user-manual.html
> DOC_HTML=$(MAN_HTML) $(OBSOLETE_HTML)
If you
"Advice" is a mass noun, not a count noun; it's not
ordinarily pluralized.
(I've never seen "advices" before, and to double-check that this isn't
an idiosyncrasy of mine I checked the Google Ngram data:
http://books.google.com/ngrams/graph?content=advice%2Cadvices
which shows "advices" is <1/100
It's not clear in git-describe(1) what kind of "pattern" should be
passed to --match. Fix that.
Signed-off-by: Greg Price
---
Documentation/git-describe.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-describe.txt b/Documentation/git-describe.txt
i
A couple of references still survive to .git/refs as a tree
of all refs. Fix one in docs, one in a -h message, one in
a -h message quoted in docs.
Signed-off-by: Greg Price
---
Documentation/config.txt | 2 +-
Documentation/gitcli.txt | 9 +
builtin/describe.c | 4 ++--
3 files ch
Jeff King writes:
> On Sun, Feb 24, 2013 at 07:46:51PM +0100, Andreas Ericsson wrote:
>
>> The lack of certificate authority verification presents no attack vector
>> for git imap-send. As such, it doesn't warrant a CVE. I'm sure you'll
>> be credited with a "reported-by" line in the commit messa
Currently when --all is passed, the effect of --match is only
to demote non-matching tags to be treated like non-tags. This
is puzzling behavior and not consistent with the documentation,
especially with the suggested usage of avoiding information leaks.
The combination of --all and --match is an
Heiko Voigt writes:
> diff --git a/config.c b/config.c
> index aefd80b..f995e98 100644
> --- a/config.c
> +++ b/config.c
> @@ -13,6 +13,9 @@
> typedef struct config_file {
> struct config_file *prev;
> FILE *f;
> + int is_strbuf;
> + struct strbuf *strbuf_contents;
> + in
René Scharfe writes:
> Am 23.02.2013 15:31, schrieb Ville Skyttä:
>>
>> Signed-off-by: Ville Skyttä
>> ---
>> Documentation/RelNotes/1.7.5.4.txt | 2 +-
>> Documentation/RelNotes/1.7.8.txt | 2 +-
>
> Retroactively changing release notes for older versions i
Erik Faye-Lund writes:
> On Thu, Jan 10, 2013 at 1:10 PM, Karsten Blees
> wrote:
>> Changes since initial version (see attached diff for details):
>> - split in two patches
>> - removed unused variables
>> - improved the dll error message
>> - changed ?: to if else
>> - added comments
>>
>> Als
Ramsay Jones writes:
> Jonathan Nieder wrote:
>
>> Throughout git, it is assumed that the WIN32 preprocessor symbol is
>> defined on native Windows setups (mingw and msvc) and not on Cygwin.
>> On Cygwin, most of the time git can pretend this is just another Unix
>> machine, and Windows-specific
Modestas Vainius writes:
> Hello,
>
> Saturday 12 January 2013 06:25:21 rašė:
>> On Sat, Jan 12, 2013 at 03:59:52PM +0200, Modestas Vainius wrote:
>> > @@ -306,6 +311,11 @@ static CURL *get_curl_handle(void)
>> >
>> >if (curl_ftp_no_epsv)
>> >
>> >curl_easy_setopt(result, CUR
Martin von Zweigbergk writes:
> I'm working on a re-roll of
>
> http://thread.gmane.org/gmane.comp.version-control.git/205796
>
> and finally got around to including test cases for what you fixed in
> this patch. I want to make sure I'm testing what you fixed here. See
> questions below.
Did any
Eric James Michael Ritz writes:
> On 01/19/2013 04:49 PM, Antoine Pelisse wrote:
>> I think `git add -u` would be closer. It would stage removal of
>> files, but would not stage untracked files. It would stage other
>> type of changes though.
>
> On Sat, Jan 19, 2013 at 10:47 PM, Tomas Carnecky
"Gustavo L. de M. Chaves" writes:
> ...
> While working on porting Git::Hooks to Windows I stumbled upon a few
> problems in the Git module, problems specific to the Windows
> environment. In the following sequence of patches I try to fix them.
Any comment on this from Windows folks?
--
To unsub
TJ writes:
> On 31/01/13 15:51, Junio C Hamano wrote:
>> TJ writes:
>>
>>> + $(INSTALL) -d -m $(INSTALL_MODE_EXECUTABLE) $(DESTDIR)$(man1dir)
>>> + $(INSTALL) -d -m $(INSTALL_MODE_EXECUTABLE) $(DESTDIR)$(man5dir)
>>> + $(INSTALL) -d -m $(INSTALL_MODE_EXECUTABLE) $(DESTDIR)$(man7dir)
>>> +
Ramsay Jones writes:
> As I mentioned recently, while discussing a cygwin specific patch
> (see "Version 1.8.1 does not compile on Cygwin 1.7.14" thread), the
> MSVC build is broken for me.
>
> The first 4 patches fix the MSVC build for me. The final patch is
> not really related to fixing the bu
Care to tie the loose end on this one, with a sign-off?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
"Philip Oakley" writes:
>>> You probably wanted "git bundle create ../repo.bundle --all" which
>>> includes both "master" and "HEAD".
>>
>> That explains it, thanks! Maybe this could be added as an example to
>> the
>> documentation for `git bundle`? People looking at `man git-bundle`
>> hoping
>
Junio C Hamano writes:
> Mike Gorchak writes:
>
>> CFLAGS="-I/usr/qnxVVV/include" LDFLAGS="-I/usr/qnxVVV/lib" ./configure
>> --prefix=/usr
>
> Oh, I didn't notice that, but the definition of ALL_CFLAGS may be
> what is wrong. It allows CFLAGS to come before BASIC_CFLAGS that
> adds -Icompat/, w
65 matches
Mail list logo
