On 27/03/2019 19:55, Andreas Schwab wrote:
Do you have a URL rewrite rule (url.*.insteadof)?
Andreas.
I don't know. How do I figure that out? There is nothing like this in my
~/.ssh/config
On Wed, Mar 27, 2019 at 03:10:42PM +0100, Ævar Arnfjörð Bjarmason wrote:
>
> On Wed, Mar 27 2019, SZEDER Gábor wrote:
>
> > On Wed, Mar 27, 2019 at 12:21:55PM +0100, Ævar Arnfjörð Bjarmason wrote:
> >>
> >> On Wed, Mar 27 2019, SZEDER Gábor wrote:
> >>
> >> > On Wed, Mar 27, 2019 at 11:09:18AM +0
On Wed, Mar 27, 2019 at 5:24 PM Phillip Wood wrote:
>
> On 26/03/2019 15:48, Elijah Newren wrote:
> > On Tue, Mar 26, 2019 at 8:24 AM Duy Nguyen wrote:
> >> On Tue, Mar 26, 2019 at 10:01 PM Elijah Newren wrote:
> >
> >> Yeah.. --ignore-in-process does not necessarily mean aborting
> >> something
On 28/03/2019 10:05, Petr Bena wrote:
On 27/03/2019 19:55, Andreas Schwab wrote:
Do you have a URL rewrite rule (url.*.insteadof)?
Andreas.
I don't know. How do I figure that out? There is nothing like this in
my ~/.ssh/config
Oh you were right I found it in git config --list, removing this f
Hello.
$ git log include/__vic/mutex.h
commit 9429293f8f8fb0819c77cf1f723567f6edc8fb6a
Merge: 96dd9a2 f484f4e
Author: __vic <__...@ngs.ru>
Date: 2017-12-13 10:41:32 +0300
Merge branch 'generic' into posix
commit f484f4e8aae32041ba56bdce12d1efd8491e94d5
Merge: 86b848a b9bbbe6
Author: __vic <
On Thu, Mar 28 2019, Victor wrote:
> Hello.
>
> $ git log include/__vic/mutex.h
> commit 9429293f8f8fb0819c77cf1f723567f6edc8fb6a
> Merge: 96dd9a2 f484f4e
> Author: __vic <__...@ngs.ru>
> Date: 2017-12-13 10:41:32 +0300
>
> Merge branch 'generic' into posix
>
> commit f484f4e8aae32041ba56bdc
Teach git to load default Trace2 settings from the system config (usually
"/etc/gitconfig"). The existing GIT_TR2_* environment variables can be used
to override the new system defaults. It also includes a little startup
refactoring.
Note: I found interactive testing of this feature to be awkward
From: Jeff Hostetler
Create trace2_initialize_clock() and call from main() to capture
process start time in isolation and before other sub-systems are
ready.
Signed-off-by: Jeff Hostetler
---
Documentation/technical/api-trace2.txt | 12 ++--
common-main.c | 2 ++
From: Jeff Hostetler
Teach Git to resolve the executable directory before initializing
Trace2. This allows the system configuration directory to be
discovered earlier (because it is sometimes relative to the prefix
or runtime-prefix).
This will be used by the next commit to allow trace2 setting
From: Jeff Hostetler
Add elapsed process time to "start" event to measure
the performance of early process startup.
Signed-off-by: Jeff Hostetler
---
Documentation/technical/api-trace2.txt | 11 ++-
t/t0211-trace2-perf.sh | 12 ++--
trace2.c
From: Jeff Hostetler
Teach git to read the system config (usually "/etc/gitconfig") for
default Trace2 settings. This allows system-wide Trace2 settings to
be installed and inherited to make it easier to manage a collection of
systems.
The original GIT_TR2* environment variables are loaded afte
Any plans to fix this?
On Thu, 28 Mar 2019 14:16:43 +0100
Ævar Arnfjörð Bjarmason wrote:
On Thu, Mar 28 2019, Victor wrote:
Hello.
$ git log include/__vic/mutex.h
commit 9429293f8f8fb0819c77cf1f723567f6edc8fb6a
Merge: 96dd9a2 f484f4e
Author: __vic <__...@ngs.ru>
Date: 2017-12-13 10:41:32 +
On Thu, Mar 28 2019, Victor wrote:
> Any plans to fix this?
No. I just thought I'd peek at it for a sec, sorry. Maybe someone else
is interested it poking it some more.
> On Thu, 28 Mar 2019 14:16:43 +0100
> Ævar Arnfjörð Bjarmason wrote:
>>
>> On Thu, Mar 28 2019, Victor wrote:
>>
>>> Hello
On Thu, Mar 28 2019, Jeff Hostetler via GitGitGadget wrote:
Thanks for working on this!
Haven't given this any deep testing. Just some observations:
> From: Jeff Hostetler
>
> Teach git to read the system config (usually "/etc/gitconfig") for
> default Trace2 settings. This allows system-wid
On Thu, Mar 28, 2019 at 4:04 AM Duy Nguyen wrote:
>
> On Wed, Mar 27, 2019 at 5:24 PM Phillip Wood
> wrote:
> >
> > On 26/03/2019 15:48, Elijah Newren wrote:
> > > On Tue, Mar 26, 2019 at 8:24 AM Duy Nguyen wrote:
> > >> On Tue, Mar 26, 2019 at 10:01 PM Elijah Newren wrote:
> > >
> > >> Yeah..
On Wed, Mar 27, 2019 at 1:31 PM Mooga wrote:
>
> Hi Eliah,
> thanks for the advice, but still after I read the SubmittingPatches , and
> see around the Submitting patches process still confussing for me , there's a
> better way for explanation as an example
>
>
> Regards
On this list, please
Change an idiom we're using to ensure that gc_before_repack() only
does work once (see 62aad1849f ("gc --auto: do not lock refs in the
background", 2014-05-25)) to be more obvious.
Nothing except this function cares about the "pack_refs" and
"prune_reflogs" variables, so let's not leave the reader
The "git reflog expire" command when given an unknown reference has
since 4264dc15e1 ("git reflog expire", 2006-12-19) when this command
was implemented emit an error, but this has never been tested for.
Let's test for it, also under gc.reflogExpire{Unreachable,}=never in
case a future change is t
Change a couple of tests that weren't using the helper to use it. This
makes the trailing "--unset" unnecessary.
Signed-off-by: Ævar Arnfjörð Bjarmason
---
t/t1410-reflog.sh | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/t/t1410-reflog.sh b/t/t1410-reflog.sh
in
Don't redundantly run "git reflog expire --all" when gc.reflogExpire
and gc.reflogExpireUnreachable are set to "never", and die immediately
if those configuration valuer are bad.
As an earlier "assert lack of early exit" change to the tests for "git
reflog expire" shows, an early check of gc.reflo
Checking gc_auto_threshold in too_many_loose_objects() was added in
17815501a8 ("git-gc --auto: run "repack -A -d -l" as necessary.",
2007-09-17) when need_to_gc() itself was also reliant on
gc_auto_pack_limit before its early return:
gc_auto_threshold <= 0 && gc_auto_pack_limit <= 0
When tha
It seems the list software dislikes Michael Haggerty for some reason,
but as seen in my reply to his message my v4 has some unaddressed
issues in the previous 8/8 that I need to get to:
https://public-inbox.org/git/87pnqkco8v@evledraar.gmail.com/
I'll have limited time next week to get to that
When gc.reflogExpire and gc.reflogExpireUnreachable are set to "never"
and --stale-fix isn't in effect we *could* exit early without
pointlessly looping over all the reflogs.
However, as an earlier change to add a test for the "points nowhere"
warning shows even in such a mode we might want to pri
There's been a lot of changing of the hardcoded "40" values to
the_hash_algo->hexsz, but we've so far missed this one where we
hardcoded 38 for the loose object file length.
This is because a SHA-1 like abcde[...] gets turned into
objects/ab/cde[...]. There's no reason to suppose the same won't be
On 28/03/2019 11:04, Duy Nguyen wrote:
On Wed, Mar 27, 2019 at 5:24 PM Phillip Wood wrote:
On 26/03/2019 15:48, Elijah Newren wrote:
On Tue, Mar 26, 2019 at 8:24 AM Duy Nguyen wrote:
On Tue, Mar 26, 2019 at 10:01 PM Elijah Newren wrote:
Yeah.. --ignore-in-process does not necessarily me
I have done what is https://gitgitgadget.github.io/ but the problem is
my pull request not being successful even what I have changed is "
test_path_is_dir " in test file "t2400", it returns
PowerShell exited with code '1'.
Publishing build artifacts failed with an error: Not found PathtoPublish:
Otherwise the error from `git rev-parse` is uselessly
polluting the debug output.
Signed-off-by: Christian Couder
---
t/t6050-replace.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/t/t6050-replace.sh b/t/t6050-replace.sh
index 41b177936e..5cb8281bab 100755
--- a/t/t6050-r
This modernizes a test and makes it more portable.
Signed-off-by: Christian Couder
---
t/t6050-replace.sh | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/t/t6050-replace.sh b/t/t6050-replace.sh
index d638119750..41b177936e 100755
--- a/t/t6050-replace.sh
+++ b/t/t6050-r
When passing a tag as a parent argument to `git replace --graft`,
it can be useful to accept it and use the underlying commit as a
parent.
This already works for lightweight tags, but unfortunately
for annotated tags we have been using the hash of the tag object
instead of the hash of the underlyi
Dear Friend,
I am Barrister Collins Koffi a solicitor at law, personal attorney to
Mr J.B. a national Of your country I want you to receive money on my
behalf.The purpose of my contacting you is because you share same Last
name with my late client. When you reply this message,i will
send you the fu
Hi Phillip,
On Thu, Mar 28, 2019 at 9:23 AM Phillip Wood wrote:
> On 28/03/2019 11:04, Duy Nguyen wrote:
> > On Wed, Mar 27, 2019 at 5:24 PM Phillip Wood
> > wrote:
> >> On 26/03/2019 15:48, Elijah Newren wrote:
> >>> On Tue, Mar 26, 2019 at 8:24 AM Duy Nguyen wrote:
> On Tue, Mar 26, 201
ср, 27 мар. 2019 г. в 20:01, Kapil Jain :
>
> > On Tue, Mar 26, 2019 at 2:48 AM Olga Telezhnaya
> > wrote:
> >> Kapil Jain wrote:
> > > Now, the verify_ref_format function can be used inside
> > > get_commit_format function, hence reusing logic.
> > > Is this a correct example to work on, for th
Hi Mooga,
On Thu, Mar 28, 2019 at 10:08 AM Mooga wrote:
>
> I have done what is https://gitgitgadget.github.io/ but the problem is
> my pull request not being successful even what I have changed is "
> test_path_is_dir " in test file "t2400", it returns
>
> PowerShell exited with code '1'.
> Pub
Hi Christian,
On Thu, Mar 28, 2019 at 06:17:22PM +0100, Christian Couder wrote:
> When passing a tag as a parent argument to `git replace --graft`,
> it can be useful to accept it and use the underlying commit as a
> parent.
>
> This already works for lightweight tags, but unfortunately
> for anno
On Thu, Mar 28, 2019 at 1:17 PM Christian Couder
wrote:
> Otherwise the error from `git rev-parse` is uselessly
> polluting the debug output.
>
> Signed-off-by: Christian Couder
> ---
> diff --git a/t/t6050-replace.sh b/t/t6050-replace.sh
> @@ -40,7 +40,7 @@ commit_peeling_shows_parents ()
> -
On 3/28/2019 10:36 AM, Ævar Arnfjörð Bjarmason wrote:
On Thu, Mar 28 2019, Jeff Hostetler via GitGitGadget wrote:
Thanks for working on this!
Haven't given this any deep testing. Just some observations:
From: Jeff Hostetler
Teach git to read the system config (usually "/etc/gitconfig")
Greetings Friend
Forgive me for writing you this letter , I will like to bring to your that
(8.5.million Euro claims ) This is a legitimate transaction and The money will
be shared 60% for me and 40% for you . get back to me, I will give you full
details on how the money will be transfer to y
On Wed, Mar 27, 2019 at 5:27 AM Ævar Arnfjörð Bjarmason
wrote:
>
>
> On Wed, Mar 27 2019, Elijah Newren wrote:
>
> > On Tue, Mar 26, 2019 at 12:56 AM Denton Liu wrote:
> >>
> >> Robert Dailey reported confusion on the mailing list about a recursive
> >> tag which was most likely created by mistak
Add a test for the error() case in alt_odb_usable() where an alternate
directory doesn't exist. This behavior has been the same since
26125f6b9b ("detect broken alternates.", 2006-02-22), but if that
error() was turned into die() the entire test suite would still pass.
Perhaps we should die() in t
On Thu, Mar 28 2019, Eric Sunshine wrote:
> On Thu, Mar 28, 2019 at 1:17 PM Christian Couder
> wrote:
>> Otherwise the error from `git rev-parse` is uselessly
>> polluting the debug output.
>>
>> Signed-off-by: Christian Couder
>> ---
>> diff --git a/t/t6050-replace.sh b/t/t6050-replace.sh
>>
On 03/20, Denton Liu wrote:
> On Wed, Mar 20, 2019 at 10:49:55PM +, Thomas Gummerer wrote:
> > diff --git a/t/t3903-stash.sh b/t/t3903-stash.sh
> > index 97cc71fbaf..83926ab55b 100755
> > --- a/t/t3903-stash.sh
> > +++ b/t/t3903-stash.sh
> > @@ -612,6 +612,24 @@ test_expect_success 'stash show
On 03/22, Junio C Hamano wrote:
> Philip Oakley writes:
>
> >> of 'cp -R'. I thought of making the same clarification for 'rsync
> >> --delete' as well, however I think with it being explicitly specified
> >> for 'cp -R', readers should be able to deduce that we are talking
> >> about the destin
One quick comment:
On 2019.03.28 06:31, Jeff Hostetler via GitGitGadget wrote:
[...]
> diff --git a/trace2.h b/trace2.h
> index 8f89e70c44..cda8349058 100644
> --- a/trace2.h
> +++ b/trace2.h
> @@ -38,7 +38,8 @@ void trace2_initialize_clock(void);
>
> /*
> * Initialize TRACE2 tracing facility
On 03/24, Kapil Jain wrote:
> On Sun, Mar 24, 2019 at 2:49 PM Christian Couder
> wrote:
> >
> > The test_language_driver() function used to test the regexps is
> > ...
> > GIT_TEST_CMP which is usually either "diff -u" or "diff -c".
>
> Thanks.
>
> please provide some insights on the regex menti
Greetings,
We are consultancy firm situated in Bahrain currently looking to finance new or
existing projects in any industry.
Currently we are sourcing for investment opportunities for our review and
consideration and we provide financial and strategic advisory services to
growing companies an
On 03/22, Matheus Tavares wrote:
> From: Ævar Arnfjörð Bjarmason
>
> Add tests for what happens when we perform a local clone on a repo
> containing odd files at .git/object directory, such as symlinks to other
> dirs, or unknown files.
>
> I'm bending over backwards here to avoid a SHA1 depende
On 03/22, Matheus Tavares wrote:
> There is currently an odd behaviour when locally clonning a repository
> with symlinks at .git/objects: using --no-hardlinks all symlinks are
> dereferenced but without it Git will try to hardlink the files with the
> link() function, which has an OS-specific beha
A common scenario is if a user is working on a topic branch and they
wish to make some changes to intermediate commits or autosquash, they
would run something such as
git rebase -i --onto master... master
in order to preserve the merge base. This prevents unnecessary commit
churning.
Alt
On 03/22, Matheus Tavares wrote:
> Add the possibility of giving flags to dir_iterator_begin to initialize
> a dir-iterator with special options.
>
> Currently possible flags are DIR_ITERATOR_PEDANTIC, which makes
> dir_iterator_advance abort imediatelly in the case of an error while
s/imediatell
On Thu, Mar 28 2019, Denton Liu wrote:
> A common scenario is if a user is working on a topic branch and they
> wish to make some changes to intermediate commits or autosquash, they
> would run something such as
>
> git rebase -i --onto master... master
>
> in order to preserve the merge b
On Wed, Mar 27, 2019 at 2:21 PM Christian Couder
wrote:
>
> On Wed, Mar 27, 2019 at 2:11 PM Christian Couder
> wrote:
> >
> > On Wed, Mar 27, 2019 at 11:24 AM Andreas Schwab wrote:
> > >
> > > When running `git replace --graft A B' where B is a non-commit (eg. a
> > > tag) it displays an error,
51 matches
Mail list logo