On Tue, Jul 09, 2013 at 08:05:19AM +0200, Bert Wesarg wrote:
> > + argv_array_pushl(&args, "send-pack", "--stateless-rpc",
> > "--helper-status");
>
> missing NULL sentinel. GCC has the 'sentinel' [1] attribute to catch
> such errors. Or use macro magic:
>
> void argv_array_pushl_(struct
On Tue, Jul 9, 2013 at 7:18 AM, Junio C Hamano wrote:
> Instead of using a hand-managed argument array, use argv-array API
> to manage dynamically formulated command line.
>
> Signed-off-by: Junio C Hamano
> ---
> remote-curl.c | 31 +++
> 1 file changed, 15 insertion
This is a re-roll of a patch [1] which fixes the
line-log.c:sort_and_merge_range_set() coalescing bug. This re-roll
inserts a new patch before the lone patch from v1.
patch 1/2: Fix broken tests in t4211 which should have detected the
sort_and_merge_range_set() bug but didn't due to incorrect
When coalescing ranges, sort_and_merge_range_set() unconditionally
assumes that the end of a range being folded into a preceding range
should become the end of the coalesced range. This assumption, however,
is invalid when one range is a subset of another. For example, given
ranges 1-5 and 2-3 add
t4211 attempts to test multiple git-log -L ranges where one range is a
superset of the other, and falsely succeeds because its "expected"
output is incorrect.
Overlapping -L ranges handed to git-log are coalesced by
line-log.c:sort_and_merge_range_set() into a set of non-overlapping,
disjoint rang
Jeff King writes:
> On Mon, Jul 08, 2013 at 02:09:59PM -0700, Junio C Hamano wrote:
>
>> The definition of "struct ref" in "cache.h", a header file so
>> central to the system, always confused me. This structure is not
>> about the local ref used by sha1-name API to name local objects.
>> [...]
On Mon, Jul 08, 2013 at 10:33:26PM -0700, Junio C Hamano wrote:
> Jeff King writes:
>
> > 1. Behave more or less the same between "git name-rev $sha1" and "echo
> > $sha1 | git name-rev --stdin". Your patch improves that. Though I
> > note that --peel-to-commit does not affect --stdi
Jeff King writes:
> 1. Behave more or less the same between "git name-rev $sha1" and "echo
> $sha1 | git name-rev --stdin". Your patch improves that. Though I
> note that --peel-to-commit does not affect --stdin at all. Should
> it? And of course the two differ in that the comman
Instead of using a hand-managed argument array, use argv-array API
to manage dynamically formulated command line.
Signed-off-by: Junio C Hamano
---
remote-curl.c | 31 +++
1 file changed, 15 insertions(+), 16 deletions(-)
diff --git a/remote-curl.c b/remote-curl.c
in
On Mon, Jul 08, 2013 at 06:38:32PM +0530, Ramkumar Ramachandra wrote:
> Junio C Hamano wrote:
> > With this on top of the other patches in this series, you would get:
> >
> > $ git describe --contains $(git rev-parse v1.8.3 v1.8.3^0)
> > v1.8.3
> > v1.8.3
> >
> > while you can still di
On Sun, Jul 07, 2013 at 03:33:44PM -0700, Junio C Hamano wrote:
> With this on top of the other patches in this series, you would get:
>
> $ git describe --contains $(git rev-parse v1.8.3 v1.8.3^0)
> v1.8.3
> v1.8.3
>
> while you can still differentiate tags and the commits they poin
On Sun, Jul 07, 2013 at 03:33:43PM -0700, Junio C Hamano wrote:
> + argv_array_init(&args);
> + argv_array_push(&args, "name-rev");
> + argv_array_push(&args, "--name-only");
> + argv_array_push(&args, "--no-undefined");
> [...]
> - memcp
On Mon, Jul 08, 2013 at 08:00:09AM -0700, Junio C Hamano wrote:
> I think this deserves to be backported to 'maint' track for
> 1.8.3.x. Here is an attempt to do so.
Agreed. As it makes certain local-clone workflows really painful, I
think my original can be considered a performance regression f
On Mon, Jul 08, 2013 at 02:09:59PM -0700, Junio C Hamano wrote:
> The definition of "struct ref" in "cache.h", a header file so
> central to the system, always confused me. This structure is not
> about the local ref used by sha1-name API to name local objects.
> [...]
> * I hate to to this kind
On Mon, Jul 08, 2013 at 08:54:24AM -0700, Shawn O. Pearce wrote:
> Has anyone studied the impact of converting the pack idx fanout table
> from 256 entries to 65536 entries?
>
> Back of the envelope estimates for 3.1M objects in linux.git suggests
> a 2^16 fanout table would decrease the number o
Am 08.07.2013 23:39, schrieb Rick Liu:
Hi,
Currently when doing "git checkout" (either for a branch or a tag),
if the file doesn't exist before,
the file will be created using current datetime.
This causes problem while trying to tar the git repository source files
(excluding .git folder).
The
On Mon, Jul 08, 2013 at 02:56:57PM +0200, Michael Schubert wrote:
> $gmane/201715 brought up the idea to fetch --prune by default.
> Since --prune is a "potentially destructive operation" (Git doesn't
> keep reflogs for deleted references yet), we don't want to prune
> without users consent.
>
>
On Mon, Jul 8, 2013 at 8:37 PM, Ramkumar Ramachandra wrote:
> Duy Nguyen wrote:
>> The short/long naming is the least I worry about. We could add long
>> names to pretty specifiers. The thing about the last attempt is, you
>> add some extra things on top elsewhere, but format_commit_item code
>> m
Junio C Hamano wrote:
> The command line parser of "git push" for "--tags", "--delete", and
> "--thin" options still used outdated OPT_BOOLEAN. Because these
> options do not give escalating levels when given multiple times,
> they should use OPT_BOOL.
Thanks. Looks obviously correct, so
Revie
Thomas Gummerer writes:
>> The reader often needs to rewind the read-pointer partially while
>> walking the index (e.g. next_cache_entry() in unpack-trees.c and how
>> the o->cache_bottom position is used throughout the subsystem). I
>> am not sure if this singly-linked list is a good way to go.
On 07/06/2013 08:55 PM, Jonathan Nieder wrote:
Mark Levedahl wrote:
Do not use FIFOs on cygwin, they do not work. Cygwin includes
coreutils, so has mkfifo, and that command does something. However,
the resultant named pipe is known (on the Cygwin mailing list at
least) to not work correctly.
H
"Rick Liu" writes:
> Can we use GIT's commit time as the mtime for all of files/folders when we do
> "git checkout"?
No. That will screw up common practice of build based on file
timestamps (e.g. make).
You may be interested in "git archive $commit" which will set the file
timestamps that of
The command line parser of "git push" for "--tags", "--delete", and
"--thin" options still used outdated OPT_BOOLEAN. Because these
options do not give escalating levels when given multiple times,
they should use OPT_BOOL.
Signed-off-by: Junio C Hamano
---
builtin/push.c | 6 +++---
1 file chan
Hi,
Currently when doing "git checkout" (either for a branch or a tag),
if the file doesn't exist before,
the file will be created using current datetime.
This causes problem while trying to tar the git repository source files
(excluding .git folder).
The tar binary can be different
even all of
Junio C Hamano writes:
> The definition of "struct ref" in "cache.h", a header file so
> central to the system, always confused me. This structure is not
> about the local ref used by sha1-name API to name local objects.
>
> It is what refspecs are expanded into, after finding out what refs
> th
On Mon, Jul 8, 2013 at 1:50 PM, Brandon Casey wrote:
> On Sun, Jul 7, 2013 at 3:14 AM, Jeff King wrote:
>> diff --git a/pack-revindex.c b/pack-revindex.c
>> index 77a0465..d2adf36 100644
>> --- a/pack-revindex.c
>> +++ b/pack-revindex.c
>> @@ -59,11 +59,78 @@ static int cmp_offset(const void *a_
The definition of "struct ref" in "cache.h", a header file so
central to the system, always confused me. This structure is not
about the local ref used by sha1-name API to name local objects.
It is what refspecs are expanded into, after finding out what refs
the other side has, to define what ref
Document the new index api and add examples of how it should be used
instead of the old functions directly accessing the index.
Helped-by: Nguyễn Thái Ngọc Duy
Signed-off-by: Thomas Gummerer
---
Duy Nguyen writes:
> Hmm.. I was confused actually (documentation on the api would help
> greatly)
On Sun, Jul 7, 2013 at 3:14 AM, Jeff King wrote:
> The pack revindex stores the offsets of the objects in the
> pack in sorted order, allowing us to easily find the on-disk
> size of each object. To compute it, we populate an array
> with the offsets from the sha1-sorted idx file, and then use
> q
Junio C Hamano writes:
> Thomas Gummerer writes:
>
>> Add an api for access to the index file. Currently there is only a very
>> basic api for accessing the index file, which only allows a full read of
>> the index, and lets the users of the data filter it. The new index api
>> gives the users
On Fri, Jul 05, 2013 at 07:16:01PM +0400, Ilya Holinov wrote:
> I have svn repository on https singed with GeoTrust issued certificate.
> Every time i try to access this repository i have message :
>
> $ git svn rebase
> Error validating server certificate for 'https://svn.egspace.ru:443':
> - Th
Peter Krefting writes:
> brian m. carlson:
>
>> +/* U+FFFE and U+ are guaranteed non-characters. */
>> +if ((codepoint & 0x1e) == 0xfffe)
>> +return bad_offset;
>
> I missed this the first time around: All Unicode characters whose
> lower 16-bit
On 2013-07-08 17.20, Thomas Rast wrote:
> Some shells do not understand the one-line construct, and instead need
>
> FOO=bar &&
> export FOO
>
> Detect this in the test-lint target.
>
> Signed-off-by: Thomas Rast
> ---
>
> I wrote:
>
>> Torsten Bögershausen writes:
> [...]
>>> -
On Mon, Jul 08, 2013 at 02:56:57PM +0200, Michael Schubert wrote:
> $gmane/201715 brought up the idea to fetch --prune by default.
> Since --prune is a "potentially destructive operation" (Git doesn't
> keep reflogs for deleted references yet), we don't want to prune
> without users consent.
>
> T
On Mon, Jul 08, 2013 at 03:47:19PM +0200, Matthieu Moy wrote:
> John Keeping writes:
>
> > static const char message_advice_pull_before_push[] =
> > N_("Updates were rejected because the tip of your current branch is
> > behind\n"
> > - "its remote counterpart. Merge the remote changes
Michael Schubert writes:
> $gmane/201715 brought up the idea to fetch --prune by default.
When you can summarize it in a few lines, e.g.
Without "git fetch --prune", remote-tracking branches for a branch
the other side already has removed will stay forever. Some people
want to alwa
Junio C Hamano writes:
> Thomas Gummerer writes:
>
>> A partially read index file currently cannot be written to disk. Make
>> sure that never happens, by re-reading the index file if the index file
>> wasn't read completely before changing the in-memory index.
>
> I am not quite sure what you
On Mon, Jul 8, 2013 at 10:37 AM, Junio C Hamano wrote:
> Shawn Pearce writes:
>
>> Has anyone studied the impact of converting the pack idx fanout table
>> from 256 entries to 65536 entries?
>>
>> Back of the envelope estimates for 3.1M objects in linux.git suggests
>> a 2^16 fanout table would d
Hi Junio,
First - Thanks so much for your reply!
The original cause was simply running a non-related command.
Specifically I was trying to build some internal software. Our internal
software uses a build build tool from perforce called jam
(http://www.perforce.com/resources/documen
Shawn Pearce writes:
> Has anyone studied the impact of converting the pack idx fanout table
> from 256 entries to 65536 entries?
>
> Back of the envelope estimates for 3.1M objects in linux.git suggests
> a 2^16 fanout table would decrease the number of binary search
> iterations from ~14 to ~6.
Steven Klass writes:
> Hi Folks,
>
> Corrects an Abort Trap: 6 error with completions.
> Fixed an issue where the two commands on a single line would cause a
> strange unrelated 'Abort trap: 6' error on non-git commands on Mac OSX 10.8.
>
> Signed-off-by: Steven Klass
Can you exp
Thomas Rast writes:
> The == operator as an alias to = is not POSIX. This doesn't actually
> matter for the execution of the script, because it only runs when the
> shell is bash. However, it trips up test-lint, so it's nicer to use
> the standard form.
OK, my knee-jerk reaction was "this is o
Duy Nguyen writes:
> There's also syntax sharing. I don't think each command should have
> its own syntax. f-e-r already has %(objectsize). If we plan to have a
> common syntax, perhaps %(disk-size) should be %(objectsize:disk) or
> something. Adding formatting to cat-file --batch from scratch co
Thomas Gummerer writes:
> Add an api for access to the index file. Currently there is only a very
> basic api for accessing the index file, which only allows a full read of
> the index, and lets the users of the data filter it. The new index api
> gives the users the possibility to use only par
Thomas Gummerer writes:
> A partially read index file currently cannot be written to disk. Make
> sure that never happens, by re-reading the index file if the index file
> wasn't read completely before changing the in-memory index.
I am not quite sure what you are trying to do.
In operations
"Kyle J. McKay" writes:
> From: "Kyle J. McKay"
>
> This patch allows git-svn to fetch successfully using the
> serf library when given an https?: url to fetch from.
>
> Unfortunately some svn servers do not seem to be configured
> well for use with the serf library. This can cause fetching
> t
Brandon Casey writes:
> ...
> Using an index takes 41 ms longer, or roughly 7.8% longer.
>
> Jeff King measured a no-op push of a single ref into a remote repo
> with 370,000 refs:
>
> beforeafter
> real0m1.087s 0m1.156s
> user0m1.344s 0m1.412s
> sys 0m0.288s 0m0.284s
>
Matthieu Moy writes:
> Signed-off-by: Matthieu Moy
> ---
>> > The colon after "make" and the indentation look weird. Shouldn't this be
>> >
>> > +# To build and test:
>> > +#
>> > +# make
>> > +# bin-wrapper/git mw preview Some_page.mw
>> > +# bin-wrapper/git clone mediawiki::http://exampl
Has anyone studied the impact of converting the pack idx fanout table
from 256 entries to 65536 entries?
Back of the envelope estimates for 3.1M objects in linux.git suggests
a 2^16 fanout table would decrease the number of binary search
iterations from ~14 to ~6. The increased table costs an extr
Michael Haggerty writes:
> [Resend because of address confusion in replied-to email.]
>
> On 07/07/2013 08:00 PM, Thomas Rast wrote:
>> I recently looked into making merge-recursive more useful as a modular
>> piece in various tasks, e.g. Michael's git-imerge and the experiments
>> I made in show
On Mon, Jul 8, 2013 at 12:57 AM, Jeff King wrote:
> On Sun, Jul 07, 2013 at 04:52:23PM -0700, Shawn O. Pearce wrote:
>
>> On Sun, Jul 7, 2013 at 3:14 AM, Jeff King wrote:
>> > The pack revindex stores the offsets of the objects in the
>> > pack in sorted order, allowing us to easily find the on-d
[Resend because of address confusion in replied-to email.]
On 07/07/2013 08:00 PM, Thomas Rast wrote:
> I recently looked into making merge-recursive more useful as a modular
> piece in various tasks, e.g. Michael's git-imerge and the experiments
> I made in showing evil merges.
>
> This miniseri
Thomas Rast writes:
> Torsten Bögershausen writes:
>
>> The shell syntax "export X=Y A=B" is not understood by all shells.
>>
>> Signed-off-by: Torsten Bögershausen
>> ---
>> t/t-basic.sh | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/t/t-basic.sh b/t/t00
Some shells do not understand the one-line construct, and instead need
FOO=bar &&
export FOO
Detect this in the test-lint target.
Signed-off-by: Thomas Rast
---
I wrote:
> Torsten Bögershausen writes:
[...]
> > - export HARNESS_ACTIVE=t &&
> > + HARNESS_ACTIVE=t &&
>
Hello Fredrik,
Thanks for the suggestion! Adding in Paul Campbell and Herman Van Rink
who worked on this before.
thanks again,
Gareth
On Sun, Jul 7, 2013 at 8:54 AM, Fredrik Gustafsson wrote:
> On Wed, Jul 03, 2013 at 03:56:36PM -0400, Gareth Collins wrote:
>> Hello,
>>
>> I see over the last y
The == operator as an alias to = is not POSIX. This doesn't actually
matter for the execution of the script, because it only runs when the
shell is bash. However, it trips up test-lint, so it's nicer to use
the standard form.
Signed-off-by: Thomas Rast
---
t/t9902-completion.sh | 2 +-
1 file
Ramkumar Ramachandra writes:
> Finds symbolic names suitable for human digestion for revisions
> given in any format parsable by git rev-parse.
>
> It is meant to name _revisions_ (aka. commits):
That is a mistaken documentation, written based on a half-baked
implementation that conflated "t
Michael Haggerty writes:
> On 07/08/2013 12:33 AM, Junio C Hamano wrote:
>> The logic will be used in a new codepath for showing exact matches.
>>
>> Signed-off-by: Junio C Hamano
>> ---
>> builtin/name-rev.c | 19 ---
>> 1 file changed, 12 insertions(+), 7 deletions(-)
>>
>>
Duy Nguyen writes:
> On Mon, Jul 8, 2013 at 2:30 PM, Jeff King wrote:
>> Subject: [PATCH] clone: drop connectivity check for local clones
>>
>> Commit 0433ad1 (clone: run check_everything_connected,
>> 2013-03-25) added the same connectivity check to clone that
>> we use for fetching. The intent
Torsten Bögershausen writes:
> The shell syntax "export X=Y A=B" is not understood by all shells.
>
> Signed-off-by: Torsten Bögershausen
> ---
> t/t-basic.sh | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/t/t-basic.sh b/t/t-basic.sh
> index 5c32288..10be
Hi,
I tried without spec, but then it tried importing everything, even
though there was a .gitignore and a .git/config/exclude file.
Then, it crashed during the importation because it could find an old
branch (I don't have access to everything on the repository), so I
tried importing just the rece
Hi Folks,
Corrects an Abort Trap: 6 error with completions.
Fixed an issue where the two commands on a single line would cause a
strange unrelated 'Abort trap: 6' error on non-git commands on Mac OSX 10.8.
Signed-off-by: Steven Klass
---
contrib/completion/git-completion.bas
Junio C Hamano wrote:
> +1; I find red on many terminal emulators to be too dark to tell,
> especially in a small font, from black myself.
It's a matter of taste anyway. I hope everyone's not going colorblind
from writing too much C89 and Bourne shell ;)
Eduardo R. D'Avila wrote:
> I think color
John Keeping writes:
> static const char message_advice_pull_before_push[] =
> N_("Updates were rejected because the tip of your current branch is
> behind\n"
> -"its remote counterpart. Merge the remote changes (e.g. 'git
> pull')\n"
> -"before pushing again.\n"
> +
On Mon, Jul 8, 2013 at 12:10 PM, Matthieu Brucher
wrote:
> Without the spec client, it seems that the branches are recognized,
> but there are some many binary files that I need to remove them during
> the migration.
> I tried setting a .gitignore beforehand, but it is not respected (I
> tried to
Duy Nguyen writes:
> On Mon, Jul 8, 2013 at 6:20 PM, Thomas Gummerer wrote:
>> Duy Nguyen writes:
>>> Putting filter_opts in index_state feels like a bad design. Iterator
>>> information should be separated from the iterated object, so that two
>>> callers can walk through the same index withou
Duy Nguyen wrote:
> The short/long naming is the least I worry about. We could add long
> names to pretty specifiers. The thing about the last attempt is, you
> add some extra things on top elsewhere, but format_commit_item code
> may need to be aware of those changes, which are not obvious when
>
Signed-off-by: Matthieu Moy
---
> > The colon after "make" and the indentation look weird. Shouldn't this be
> >
> > +# To build and test:
> > +#
> > +# make
> > +# bin-wrapper/git mw preview Some_page.mw
> > +# bin-wrapper/git clone mediawiki::http://example.com/wiki/
> > +#
> >
> > ?
>
>
Junio C Hamano wrote:
>> would get name-rev to print output in the same format as describe,
>>
>> $ git describe --contains --all v1.8.3~1
>> tags/v1.8.3~1
>>
>> would not strip the leading "tags/".
>
> If you _know_ v1.8.3 does not appear outside "tags/", this does look
> inconsistent, but I d
On Mon, Jul 8, 2013 at 7:00 PM, Ramkumar Ramachandra wrote:
>> This is what I wanted to do with the in for-each-ref's pretty
>> formatting [1]. I used to hack cat-file --batch to extract info I
>> needed for experimenting with various pack index extensions. If you
>> are not in hurry, maybe we can
Junio C Hamano wrote:
> With this on top of the other patches in this series, you would get:
>
> $ git describe --contains $(git rev-parse v1.8.3 v1.8.3^0)
> v1.8.3
> v1.8.3
>
> while you can still differentiate tags and the commits they point at
> with:
>
> $ git name-rev --refs=ta
$gmane/201715 brought up the idea to fetch --prune by default.
Since --prune is a "potentially destructive operation" (Git doesn't
keep reflogs for deleted references yet), we don't want to prune
without users consent.
To accommodate users who want to either prune always or when fetching
from a pa
Jeff King writes:
> On Mon, Jul 08, 2013 at 01:03:55PM +1000, Stephen Rothwell wrote:
>
>> So commit 0433ad128c59 ("clone: run check_everything_connected") (which
>> turned up with v1.8.3) added a large traversal to clone which (as the
>> comment said) makes a clone much slower. It is especially
Junio C Hamano wrote:
> But I do not think "name-rev" is limited
> to commits, in the sense that you would see this:
>
> $ git rev-parse v1.8.3 v1.8.3^0 | git name-rev --stdin
> 8af06057d0c31a24e8737ae846ac2e116e8bafb9
> edca4152560522a431a51fc0a06147fc680b5b18 (tags/v1.8.3^0)
>
> The s
On Mon, Jul 8, 2013 at 6:20 PM, Thomas Gummerer wrote:
> Duy Nguyen writes:
>> Putting filter_opts in index_state feels like a bad design. Iterator
>> information should be separated from the iterated object, so that two
>> callers can walk through the same index without stepping on each other
>>
Junio C Hamano wrote:
> "git name-rev" is supposed to convert 40-hex object names into
> strings that name the same objects based on refs, that can be fed to
> "git rev-parse" to get the same object names back, so
>
> $ git rev-parse v1.8.3 v1.8.3^0 | git name-rev --stdin
> 8af06057d0c31a24
Duy Nguyen wrote:
> Ram, are you still interested in the awesome branch series?
Yep, but it got stalled due to lack of reviewer-interest :/
I'm a bit under the weather at the moment, but it's good to see that
you're back: let's finish this soon.
>>> Perhaps we need
>>>
>>> git cat-file --batch
Eric Sunshine writes:
> On Sun, Jul 7, 2013 at 4:11 AM, Thomas Gummerer wrote:
>> Make git read the index file version 5 without complaining.
>>
>> This version of the reader doesn't read neither the cache-tree
>> nor the resolve undo data, but doesn't choke on an index that
>> includes such dat
Duy Nguyen writes:
> On Sun, Jul 7, 2013 at 3:11 PM, Thomas Gummerer wrote:
>> Add an api for access to the index file. Currently there is only a very
>> basic api for accessing the index file, which only allows a full read of
>> the index, and lets the users of the data filter it. The new ind
Duy Nguyen writes:
> On Sun, Jul 7, 2013 at 3:11 PM, Thomas Gummerer wrote:
>> +/*
>> + * Options by which the index should be filtered when read partially.
>> + *
>> + * pathspec: The pathspec which the index entries have to match
>> + * seen: Used to return the seen parameter from match_pathsp
Without the spec client, it seems that the branches are recognized,
but there are some many binary files that I need to remove them during
the migration.
I tried setting a .gitignore beforehand, but it is not respected (I
tried to remove some folders with folder/ in .gitignore, but the
folder are s
un Mon, Jul 8, 2013 at 12:49 AM, Junio C Hamano wrote:
> Jeff King writes:
>
>> Perhaps we need
>>
>> git cat-file --batch-format="%(disk-size) %(object)"
>>
>> or similar.
This is what I wanted to do with the in for-each-ref's pretty
formatting [1]. I used to hack cat-file --batch to extract
Unfortunately, git branch -a returns nothing :/
I tried with the simple detect-branches as well as with the config values.
Perhaps the spec-client? Although it is strange as it seems that the
repository is completely empty.
Thanks,
Matthieu
2013/7/8 Vitor Antunes :
> On Mon, Jul 8, 2013 at 11:09
On Mon, Jul 8, 2013 at 11:09 AM, Matthieu Brucher
wrote:
> Hi again,
>
> I tried with @all, but it didn'y work as expected. It imported a bunch
> of revisions (but no files?) and ended with:
> Reading pipe: ['git', 'config', '--bool', 'git-p4.importLabels']
> Not checking out any branch, use "
Hi again,
I tried with @all, but it didn'y work as expected. It imported a bunch
of revisions (but no files?) and ended with:
Reading pipe: ['git', 'config', '--bool', 'git-p4.importLabels']
Not checking out any branch, use "git checkout -q -b master "
executing git config --bool git-p4.usec
The shell syntax "export X=Y A=B" is not understood by all shells.
Signed-off-by: Torsten Bögershausen
---
t/t-basic.sh | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/t/t-basic.sh b/t/t-basic.sh
index 5c32288..10be52b 100755
--- a/t/t-basic.sh
+++ b/t/t
When pushing using a matching refspec or a pattern refspec, each ref
in the local repository must be paired with a ref advertised by the
remote server. This is accomplished by using the refspec to transform
the name of the local ref into the name it should have in the remote
repository, and then p
On Mon, Jul 8, 2013 at 2:30 PM, Jeff King wrote:
> Subject: [PATCH] clone: drop connectivity check for local clones
>
> Commit 0433ad1 (clone: run check_everything_connected,
> 2013-03-25) added the same connectivity check to clone that
> we use for fetching. The intent was to provide enough safet
On 07/08/2013 12:33 AM, Junio C Hamano wrote:
> The logic will be used in a new codepath for showing exact matches.
>
> Signed-off-by: Junio C Hamano
> ---
> builtin/name-rev.c | 19 ---
> 1 file changed, 12 insertions(+), 7 deletions(-)
>
> diff --git a/builtin/name-rev.c b/bui
On Sun, Jul 07, 2013 at 04:52:23PM -0700, Shawn O. Pearce wrote:
> On Sun, Jul 7, 2013 at 3:14 AM, Jeff King wrote:
> > The pack revindex stores the offsets of the objects in the
> > pack in sorted order, allowing us to easily find the on-disk
> > size of each object. To compute it, we populate a
On Mon, Jul 08, 2013 at 12:02:11AM -0700, Brandon Casey wrote:
> Here is the reroll with an updated commit message that hopefully
> provides a little more detail to justify this change. I removed
> the use of the search index in the send_prune block since I think
> that pruning many refs is an un
On Mon, Jul 08, 2013 at 01:03:55PM +1000, Stephen Rothwell wrote:
> So commit 0433ad128c59 ("clone: run check_everything_connected") (which
> turned up with v1.8.3) added a large traversal to clone which (as the
> comment said) makes a clone much slower. It is especially noticeable on
> "git clon
When pushing using a matching refspec or a pattern refspec, each ref
in the local repository must be paired with a ref advertised by the
remote server. This is accomplished by using the refspec to transform
the name of the local ref into the name it should have in the remote
repository, and then p
93 matches
Mail list logo
