Leslie Wang writes:
> At 2.14.1 or 2.15.1, if I run command like
> - mkdir /tmp/111
> - git clone g...@github.com:111/111 /tmp/111
>
> because it will failure, then /tmp/111 will be removed automatically.
Yes, this was a (longstanding) bug that nobody bothered to fix for a
long time. As "git
On Tue, May 08, 2018 at 10:25:58PM -0700, Leslie Wang wrote:
> Recently we try to upgrade ubuntu from 17.10 to 18.04, then we found
> one inconsistent behavior on git clone.
>
> At 2.14.1 or 2.15.1, if I run command like
> - mkdir /tmp/111
> - git clone g...@github.com:111/111 /tmp/111
>
> be
Dear git experts,
Recently we try to upgrade ubuntu from 17.10 to 18.04, then we found one
inconsistent behavior on git clone.
At 2.14.1 or 2.15.1, if I run command like
- mkdir /tmp/111
- git clone g...@github.com:111/111 /tmp/111
because it will failure, then /tmp/111 will be removed autom
On 8 May 2018 at 20:10, Jeff King wrote:
> On Sun, May 06, 2018 at 04:10:29PM +0200, Martin Ågren wrote:
>> Unlike in the previous patch, this function is not prepared for
>> indicating errors via a `strbuf err`, so let's just drop the dead code.
>> Any improved error-handling can be added later.
At 17:24 +0200 08 May 2018, Duy Nguyen wrote:
It took me so long to reply partly because I remember seeing some guy
doing clever trick with tab completion that also shows a short help
text in addition to the complete words. I could not find that again
and from my reading (also internet searching
When calling match_line(), callers presently cannot determine the
relative offset of the match because match_line() discards the
'regmatch_t' that contains this information.
Instead, teach match_line() to take in a 'regmatch_t *' so that callers
can inspect the match's starting and ending offset f
To prepare for 'git grep' learning '--column', teach grep.c's
show_line() how to show the column of the first match on non-context
line.
Signed-off-by: Taylor Blau
---
grep.c | 21 -
1 file changed, 16 insertions(+), 5 deletions(-)
diff --git a/grep.c b/grep.c
index fb0fa232
To support git-grep(1)'s new option, '--column', document and teach
grep.c how to interpret relevant configuration options, similar to those
associated with '--line-number'.
Signed-off-by: Taylor Blau
---
Documentation/config.txt | 5 +
Documentation/git-grep.txt | 3 +++
grep.c
To support showing the matched column when calling 'git-grep(1)', teach
'grep_opt' the normal set of options to configure the default behavior
and colorization of this feature.
Signed-off-by: Taylor Blau
---
grep.c | 3 +++
grep.h | 2 ++
2 files changed, 5 insertions(+)
diff --git a/grep.c b/g
Take advantage of 'git-grep(1)''s new option, '--column' in order to
teach Peff's 'git-jump' script how to jump to the correct column for any
given match.
'git-grep(1)''s output is in the correct format for Vim's jump list, so
no additional cleanup is necessary.
Signed-off-by: Taylor Blau
---
c
lineNumber has casing that is inconsistent with surrounding options,
like color.grep.matchContext, and color.grep.matchSelected. Re-case this
documentation in order to be consistent with the text around it, and to
ensure that new entries are consistent, too.
Signed-off-by: Taylor Blau
---
Docume
Teach 'git-grep(1)' a new option, '--column', to show the column
number of the first match on a non-context line. This makes it possible
to teach 'contrib/git-jump/git-jump' how to seek to the first matching
position of a grep match in your editor, and allows similar additional
scripting capabiliti
Hi,
Attached is my fifth re-roll of the series to add '--column' to
'git-grep(1)'.
The main changes are from a René's concerns in [1]. He points out that
'--column' with certain extended expressions can produce nonsense
(particularly because we leave the regmatch_t uninitialized).
> So at least
v2:
* rebased onto origin/master
* dropped leftover "toplevel" variable from experimentation
* reworded the commit message for the first patch extensively
* dropped the third patch
* see "branch-diff" below.
v1:
The "What's cooking" email carried this series for some time now:
> * pc/submodule-hel
From: Prathamesh Chavan
When running 'git submodule foreach --recursive' from a subdirectory of
your repository, nested submodules get a bogus value for $path:
For a submodule 'sub' that contains a nested submodule 'nested',
running 'git -C dir submodule foreach echo $path' from the root of the
s
From: Prathamesh Chavan
As using a variable '$path' may be harmful to users due to
capitalization issues, see 64394e3ae9 (git-submodule.sh: Don't
use $path variable in eval_gettext string, 2012-04-17). Adjust
the documentation to advocate for using $sm_path, which contains
the same value. We sti
From: Prathamesh Chavan
It was observed that the variable '$displaypath' was accessible but
undocumented. Hence, document it.
Discussed-with: Ramsay Jones
Signed-off-by: Stefan Beller
Signed-off-by: Prathamesh Chavan
Signed-off-by: Junio C Hamano
---
Documentation/git-submodule.txt | 8 +++
From: Prathamesh Chavan
This aims to make git-submodule foreach a builtin. 'foreach' is ported to
the submodule--helper, and submodule--helper is called from
git-submodule.sh.
Helped-by: Brandon Williams
Mentored-by: Christian Couder
Mentored-by: Stefan Beller
Signed-off-by: Prathamesh Chavan
On Tue, May 08, 2018 at 08:31:10PM +0200, Martin Ågren wrote:
> On 8 May 2018 at 03:13, brian m. carlson wrote:
> > Since this patch fixes the present issue, I'd like to leave it as it is
> > and run through a cleanup series a bit later that catches all the
> > literal indented blocks and marks th
On Tue, May 08, 2018 at 10:34:58AM +0530, Kaartic Sivaraam wrote:
> Just to be sure, you're meaning the use of `git log --use-mailmap` when
> you mean `git log` in the log message. Am I right? Or did you mean `git
> shortlog` ?
>
> I'm asking this because I think the `git log` output doesn't consi
On Tue, May 08, 2018 at 08:28:47PM +0200, Martin Ågren wrote:
> On 8 May 2018 at 01:40, brian m. carlson wrote:
> > As I mentioned in an earlier email, I plan to set an environment
> > variable for the algorithms in use and then do something like:
> >
> > test "$tree" = "$(test-tool hash-helper
On Tue, May 08, 2018 at 08:26:05PM +0200, Martin Ågren wrote:
> On 8 May 2018 at 01:30, brian m. carlson wrote:
> > On Mon, May 07, 2018 at 12:10:39PM +0200, Martin Ågren wrote:
> >> Do we actually need more SHA-1-related prereqs, at least long-term, in
> >> which case we would want to find a more
On Tue, May 08, 2018 at 09:28:14AM -0400, Jeff King wrote:
> OK, so my question then is: what does just-gpgsm support look like?
>
> Do we literally add gpgsm.program? My thought was that taking us the
> first step towards a more generic config scheme would prevent us having
> to backtrack later.
Hello,
On 08.05.2018 07:00, Taylor Blau wrote:
On Fri, May 04, 2018 at 12:48:21AM +0300, Paul-Sebastian Ungureanu wrote:
Hello everybody,
The community bonding period started. It is well known that for a greater
rate of success, it is recommended to send weekly reports regarding project
status
Hi Gábor,
On Mon, 7 May 2018, SZEDER Gábor wrote:
> The test script 't6050-replace.sh' starts off with redirecting the whole
> test script's stdin from /dev/null. This redirection has been there
> since the test script was introduced in a3e8267225 (replace_object: add
> a test case, 2009-01-23),
On Tue, May 8, 2018 at 1:04 PM, Jonathan Tan wrote:
> On Tue, 8 May 2018 12:37:36 -0700
> Stefan Beller wrote:
>
>> +void clear_alloc_state(struct alloc_state *s)
>> +{
>> + while (s->slab_nr > 0) {
>> + s->slab_nr--;
>> + free(s->slabs[s->slab_nr]);
>> + }
>
> I
On Tue, 8 May 2018 12:37:36 -0700
Stefan Beller wrote:
> +void clear_alloc_state(struct alloc_state *s)
> +{
> + while (s->slab_nr > 0) {
> + s->slab_nr--;
> + free(s->slabs[s->slab_nr]);
> + }
I should have caught this earlier, but you need to free s->slabs itse
This is a small mechanical change; it doesn't change the
implementation to handle repositories other than the_repository yet.
Use a macro to catch callers passing a repository other than
the_repository at compile time.
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
alloc.c | 2 +
This is a small mechanical change; it doesn't change the
implementation to handle repositories other than the_repository yet.
Use a macro to catch callers passing a repository other than
the_repository at compile time.
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
alloc.c
This is a small mechanical change; it doesn't change the
implementation to handle repositories other than the_repository yet.
Use a macro to catch callers passing a repository other than
the_repository at compile time.
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
alloc.c | 4
From: Jonathan Nieder
Add a repository argument to allow the caller of grow_object_hash to
be more specific about which repository to handle. This is a small
mechanical change; it doesn't change the implementation to handle
repositories other than the_repository yet.
Signed-off-by: Jonathan Nied
This is a small mechanical change; it doesn't change the
implementation to handle repositories other than the_repository yet.
Use a macro to catch callers passing a repository other than
the_repository at compile time.
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
alloc.c | 2 +
This is a small mechanical change; it doesn't change the
implementation to handle repositories other than the_repository yet.
Use a macro to catch callers passing a repository other than
the_repository at compile time.
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
alloc.c | 2 +
This is a small mechanical change; it doesn't change the
implementation to handle repositories other than the_repository yet.
Use a macro to catch callers passing a repository other than
the_repository at compile time.
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
alloc.c | 2
Reviewed-by: Jonathan Tan
Signed-off-by: Jonathan Nieder
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
object.c | 12 ++--
object.h | 3 +--
2 files changed, 7 insertions(+), 8 deletions(-)
diff --git a/object.c b/object.c
index 0fcd6f6df42..49b952e9299 100644
--- a/
We have to convert all of the alloc functions at once, because alloc_report
uses a funky macro for reporting. It is better for the sake of mechanical
conversion to convert multiple functions at once rather than changing the
structure of the reporting function.
We record all memory allocation in al
Reviewed-by: Jonathan Tan
Signed-off-by: Jonathan Nieder
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
object.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/object.c b/object.c
index a365a910859..0fcd6f6df42 100644
--- a/object.c
+++ b/o
This is a small mechanical change; it doesn't change the
implementation to handle repositories other than the_repository yet.
Use a macro to catch callers passing a repository other than
the_repository at compile time.
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
alloc.c | 2 +
Convert the existing global cache for parsed objects (obj_hash) into
repository-specific parsed object caches. Existing code that uses
obj_hash are modified to use the parsed object cache of
the_repository; future patches will use the parsed object caches of
other repositories.
Another future use
v3:
* I used the (soon to be renamed?) branch-diff tool to attach a diff below
between v2 and v3
* fixed comment in patch 1
* correctly free objects and its hashmap in the last patch.
* drop free'ing the commit->util pointer as we do not know where
it points to.
v2:
* I decided to stick w
Add a repository argument to allow the callers of create_object
to be more specific about which repository to act on. This is a small
mechanical change; it doesn't change the implementation to handle
repositories other than the_repository yet.
Signed-off-by: Jonathan Nieder
Signed-off-by: Stefan
>>> +Deltified representation
>>
>> Does this refer to OFS delta as well as REF deltas?
>
> Yes. Both OFS and REF deltas have the same "body" which is what this
> part is about. The differences between OFS and REF deltas are not
> described (in fact I don't think we describe what OFS and REF deltas
On Tue, May 08 2018, Jeff King wrote:
> On Mon, May 07, 2018 at 01:08:46PM +0900, Junio C Hamano wrote:
>
>> Ævar Arnfjörð Bjarmason writes:
>>
>> > Right, and I'm with you so far, this makes sense to me for all existing
>> > uses of the peel syntax, otherwise v2.17.0^{tree} wouldn't be the same
On Tue, May 8, 2018 at 8:00 AM, Duy Nguyen wrote:
> On Tue, May 8, 2018 at 12:59 AM, Stefan Beller wrote:
>> @@ -501,9 +509,31 @@ void raw_object_store_clear(struct raw_object_store *o)
>> void parsed_object_pool_clear(struct parsed_object_pool *o)
>> {
>> /*
>> -* TOOD free obj
On 8 May 2018 at 03:13, brian m. carlson wrote:
> On Mon, May 07, 2018 at 06:11:43AM +0200, Martin Ågren wrote:
>> Excellent. These two patches fix my original problem and seem like the
>> obviously correct approach (in hindsight ;-) ). I wonder if the diagrams
>> earlier in the file should be tac
On 8 May 2018 at 01:40, brian m. carlson wrote:
> On Mon, May 07, 2018 at 12:24:13PM +0200, Martin Ågren wrote:
>> This could be more centralized at the top of the file, more likely to be
>> noticed during a `make test` and easier to adapt in the future. Maybe
>> something like this at the top of
On 8 May 2018 at 01:30, brian m. carlson wrote:
> On Mon, May 07, 2018 at 12:10:39PM +0200, Martin Ågren wrote:
>> On 7 May 2018 at 01:17, brian m. carlson
>> wrote:
>> > Add an SHA1 prerequisite to annotate both of these types of tests and
>> > disable them when we're using a different hash. I
On Tue, May 8, 2018 at 8:21 PM, Ævar Arnfjörð Bjarmason
wrote:
>
> On Tue, May 08 2018, Nguyễn Thái Ngọc Duy wrote:
>
>> The current document mentions OBJ_* constants without their actual
>> values. A git developer would know these are from cache.h but that's
>> not very friendly to a person who w
On Sun, May 06, 2018 at 04:10:26PM +0200, Martin Ågren wrote:
> This series addresses two classes of "static struct lock_file", removing
> the staticness: Those locks that already live inside a function, and
> those that can simply be moved into the function they are used from.
>
> The first thre
On Tue, May 8, 2018 at 7:23 PM, Stefan Beller wrote:
>> While at there, I also add some text about this obscure delta format.
>> We occasionally have questions about this on the mailing list if I
>> remember correctly.
>
> Let me see if I can understand it, as I am not well versed in the
> delt
On Tue, May 08 2018, Nguyễn Thái Ngọc Duy wrote:
> The current document mentions OBJ_* constants without their actual
> values. A git developer would know these are from cache.h but that's
> not very friendly to a person who wants to read this file to implement
> a pack file parser.
>
> Similarly
On Mon, May 07, 2018 at 05:24:05PM +0200, Duy Nguyen wrote:
> - static struct lock_file lock;
> + struct lock_file lock = LOCK_INIT;
> >>>
> >>> Is it really safe to do this? I vaguely remember something about
> >>> (global) linked list and signal handling which could trigger
On Sun, May 06, 2018 at 04:10:29PM +0200, Martin Ågren wrote:
> After taking the lock we check whether we got it and die otherwise. But
> since we take the lock using `LOCK_DIE_ON_ERROR`, we would already have
> died.
>
> Unlike in the previous patch, this function is not prepared for
> indicatin
On Mon, May 07, 2018 at 05:12:27AM -0600, David Turner wrote:
> >Right. After commit 076aa2cbda (tempfile: auto-allocate tempfiles on
> >heap, 2017-09-05) this is safe though. Quite a few locks have already
> >been moved to the stack, e.g., in 14bca6c63c (sequencer: make lockfiles
> >non-static, 2
On Mon, 7 May 2018 15:59:16 -0700
Stefan Beller wrote:
> + for (i = 0; i < o->obj_hash_size; i++) {
> + struct object *obj = o->obj_hash[i];
> +
> + if (!obj)
> + continue;
> +
> + if (obj->type == OBJ_TREE) {
> + fr
On Sat, May 05, 2018 at 08:49:43AM +0200, Ævar Arnfjörð Bjarmason wrote:
> > +test_expect_success 'grep --only-matching --heading' '
> > + git grep --only-matching --heading --line-number --column mmap file
> > >actual &&
> > + test_cmp expected actual
> > +'
> > +
> > cat >expected < > hel
On Tue, May 8, 2018 at 8:56 AM, Nguyễn Thái Ngọc Duy wrote:
> The current document mentions OBJ_* constants without their actual
> values. A git developer would know these are from cache.h but that's
> not very friendly to a person who wants to read this file to implement
> a pack file parser.
>
>
On Mon, 7 May 2018 15:59:04 -0700
Stefan Beller wrote:
> /*
> - * Holds any information related to accessing the raw object content.
> + * Holds any information needed to retrieve the raw content
> + * of objects. The object_parser uses this to get object
> + * content
On Tue, May 8, 2018 at 5:22 AM, Alex Riesen
wrote:
> From: Alex Riesen
>
> Currently, the submodules either are not shown at all (if listing a
> committed tree) or a Tcl error appears (when clicking on a submodule
> from the index list).
I do not understand where this appears, yet.
Where do I ha
On 5/7/2018 10:58 AM, Junio C Hamano wrote:
* bp/merge-rename-config (2018-05-04) 3 commits
- merge: pass aggressive when rename detection is turned off
- merge: add merge.renames config setting
- merge: update documentation for {merge,diff}.renameLimit
(this branch uses en/rename-dire
On Tue, May 8, 2018 at 8:24 AM, Duy Nguyen wrote:
> I'm arguing about this because I want to see your reaction, because
> I'm thinking of doing the very same thing for config completion. Right
> now "git config " gives you two pages of all available config
> variables. I'm thinking that we "git c
The current document mentions OBJ_* constants without their actual
values. A git developer would know these are from cache.h but that's
not very friendly to a person who wants to read this file to implement
a pack file parser.
Similarly, the deltified representation is not documented at all (the
"
On Tue, May 1, 2018 at 8:40 PM, Ævar Arnfjörð Bjarmason
wrote:
> The order in the enum might seem arbitrary, and isn't explained by
> 72518e9c26 ("more lightweight revalidation while reusing deflated
> stream in packing", 2006-09-03) which added it.
>
> Derrick Stolee suggested that it's ordered t
On Mon, Apr 23, 2018 at 7:36 AM, Eric Sunshine wrote:
> I haven't looked at the implementation, so this may be an entirely
> stupid suggestion, but would it be possible to instead render the
> completions as?
>
> % git checkout --
> --[no-]conflict= --[no-]patch
> --[
On Tue, May 8, 2018 at 12:59 AM, Stefan Beller wrote:
> @@ -501,9 +509,31 @@ void raw_object_store_clear(struct raw_object_store *o)
> void parsed_object_pool_clear(struct parsed_object_pool *o)
> {
> /*
> -* TOOD free objects in o->obj_hash.
> -*
> * As objects
On Tue, May 01, 2018 at 06:40:10PM +, Ævar Arnfjörð Bjarmason wrote:
> Change the output emitted when an ambiguous object is encountered so
> that we show tags first, then commits, followed by trees, and finally
> blobs. Within each type we show objects in hashcmp() order. Before
> this change
On Tue, May 01, 2018 at 06:40:15PM +, Ævar Arnfjörð Bjarmason wrote:
> The core.disambiguate variable was added in
> 5b33cb1fd7 ("get_short_sha1: make default disambiguation
> configurable", 2016-09-27) but never documented.
Thanks, this seems reasonable. It was originally added as a tool to
On Mon, May 07, 2018 at 01:08:46PM +0900, Junio C Hamano wrote:
> Ævar Arnfjörð Bjarmason writes:
>
> > Right, and I'm with you so far, this makes sense to me for all existing
> > uses of the peel syntax, otherwise v2.17.0^{tree} wouldn't be the same
> > as rev-parse v2.17.0^{tree}^{tree}...
>
> diff --git a/t/t5516-fetch-push.sh b/t/t5516-fetch-push.sh
> index c9a2011915..71fc902062 100755
> --- a/t/t5516-fetch-push.sh
> +++ b/t/t5516-fetch-push.sh
> @@ -965,35 +965,43 @@ test_expect_success 'push into aliased refs
> (inconsistent)' '
> )
> '
>
> -test_expect_success 'push re
On Tue, May 08, 2018 at 09:42:48AM -0400, Jeff King wrote:
> On Mon, Apr 09, 2018 at 10:32:20AM +0200, Johannes Schindelin wrote:
>
> > +static int store_aux_event(enum config_event_t type,
> > + size_t begin, size_t end, void *data)
> > +{
> > + struct config_store_data *s
On Mon, Apr 09, 2018 at 10:32:20AM +0200, Johannes Schindelin wrote:
> +static int store_aux_event(enum config_event_t type,
> +size_t begin, size_t end, void *data)
> +{
> + struct config_store_data *store = data;
> +
> + ALLOC_GROW(store->parsed, store->parsed_nr
Bert Wesarg, Tue, May 08, 2018 15:17:03 +0200:
> On Tue, May 8, 2018 at 2:22 PM, Alex Riesen
> wrote:
> > +proc flist_gitk {} {
> > +global flist_menu_file findstring gdttype
> > +
> > +set x [shellquote $flist_menu_file]
>
> this needs to handle cdup, i.e., if gitk is run from a subdire
On Mon, May 07, 2018 at 11:06:50PM +, brian m. carlson wrote:
> I think my main objection to this series is that it is generic in a way
> that isn't necessarily useful. We know there are essentially only two
> formats of PEM-style signatures: OpenPGP and CMS[0]. Even if there are
> more, the
On Tue, May 8, 2018 at 2:22 PM, Alex Riesen
wrote:
> From: Alex Riesen
>
> Similar to a git gui feature which visualizes history in a submodule,
> the submodules cause the gitk be started inside the submodule.
>
> Signed-off-by: Alex Riesen
> ---
> gitk | 12
> 1 file changed, 12 i
On Mon, May 07, 2018 at 10:46:58PM -0400, Konstantin Ryabitsev wrote:
> On Tue, May 08, 2018 at 01:51:30AM +, brian m. carlson wrote:
> > I think I would also prefer a list of available repositories over a
> > hard-coded choice. It may be that some places (say, Australia) have
> > better bandw
From: Alex Riesen
Similar to a git gui feature which visualizes history in a submodule,
the submodules cause the gitk be started inside the submodule.
Signed-off-by: Alex Riesen
---
gitk | 12
1 file changed, 12 insertions(+)
diff --git a/gitk b/gitk
index d34833f..1ec545e 100755
From: Alex Riesen
Currently, the submodules either are not shown at all (if listing a
committed tree) or a Tcl error appears (when clicking on a submodule
from the index list).
This will make it show first arbitrarily chosen number of commits,
which might be only marginally better.
Signed-off-b
Currently, the submodule entries in the file list panel are mostly ignored.
This series attempts to improve the situation by showing part of submodule
history when focusing it in the file list panel and by adding a menu element
to start gitk in the submodule (similar to git gui).
[1/2]: gitk: sh
On Tuesday 01 May 2018 10:29 PM, Wink Saville wrote:
> When --remote-tags is passed to `git remote add` the tagopt is set to
> --remote-tags and a second fetch line is added so tags are placed in
> a separate hierarchy per remote.
>
I find '--remote' in the option name to be redundant given that
On Monday 30 April 2018 01:50 AM, Ævar Arnfjörð Bjarmason wrote:
> diff --git a/t/t5516-fetch-push.sh b/t/t5516-fetch-push.sh
> index 15c8d5a734..c9a2011915 100755
> --- a/t/t5516-fetch-push.sh
> +++ b/t/t5516-fetch-push.sh
> @@ -981,7 +981,17 @@ test_expect_success 'push requires --force to update
On Mon, May 07, 2018 at 03:59:16PM -0700, Stefan Beller wrote:
> @@ -501,9 +509,31 @@ void raw_object_store_clear(struct raw_object_store *o)
> void parsed_object_pool_clear(struct parsed_object_pool *o)
> [...]
> + for (i = 0; i < o->obj_hash_size; i++) {
> + struct object *obj =
On Tuesday 08 May 2018 08:49 AM, Junio C Hamano wrote:
> Junio C Hamano writes:
>
>> I couldn't quite get what you meant by "(but not the other way
>> around)". Did you mean
>>
>> $ git push --force ../child2 refs/tags/*:refs/tags/*
>>
>> should not become non-forcing version because of the
On Tuesday 08 May 2018 12:35 AM, Stefan Beller wrote:
>> The lack of checking for the reason behind why `git add` fails seems to
>> be the reason behind that weird message.
>
> (from the man page)
> git submodule [--quiet] add [] [--] []
>
> When options are given after or we can count
83 matches
Mail list logo
