On Tue, Sep 11, 2018 at 11:15:13AM -0700, Junio C Hamano wrote:
> > That said, a quick search of codesearch.debian.net mostly finds
> > examples using straight comparison, so maybe the patch is fine as-is.
>
> I do not think we would mind terribly if we do not support
> combinations like
This adds a new archive command for protocol v2. The command expects
arguments in the form "argument X" which are passed unmodified to
git-upload-archive--writer.
This command works over the file://, Git, and SSH transports. HTTP
support will be added in a separate patch.
Signed-off-by: Josh
Signed-off-by: Josh Steadmon
---
builtin/archive.c | 8 +++-
http-backend.c | 10 +-
transport-helper.c | 5 +++--
3 files changed, 19 insertions(+), 4 deletions(-)
diff --git a/builtin/archive.c b/builtin/archive.c
index 73831887d..5fa75b3f7 100644
--- a/builtin/archive.c
This series adds a new protocol v2 command for archiving, and allows
this command to work over HTTP(S). This was previously discussed in [1].
I've CCed everyone who participated in that discussion.
[1]:
Using packet_reader will simplify version detection and capability
handling, which will make implementation of protocol v2 support in
git-archive easier.
Signed-off-by: Josh Steadmon
---
builtin/archive.c | 23 ++-
1 file changed, 14 insertions(+), 9 deletions(-)
diff --git
On Wed, Sep 12, 2018 at 12:14:25AM -0400, Jeff King wrote:
> > + ALLOC_ARRAY(list, from->nr);
> > for (i = 0; i < from->nr; i++) {
> > - struct object *from_one = from->objects[i].item;
> > + list[i] = (struct commit *)from->objects[i].item;
>
> Some of the objects in
On Fri, Jul 20, 2018 at 04:33:28PM +, Derrick Stolee wrote:
> The can_all_from_reach_with_flags() algorithm is currently quadratic in
> the worst case, because it calls the reachable() method for every 'from'
> without tracking which commits have already been walked or which can
> already
Lately I noticed that occasionally I ended up with an empty commit
message after an interactive rebase. However, since I didn't do
anything that I haven't already done countless times before, I thought
that one of my local patches touching the area where 'git commit'
calls launch_editor() got
On Tuesday, September 11, 2018 3:20:19 PM MST Junio C Hamano wrote:
>
> * jc/wt-status-state-cleanup (2018-09-07) 1 commit
> - WIP: roll wt_status_state into wt_status and populate in the collect
> phase (this branch uses ss/wt-status-committable.)
>
> * ss/wt-status-committable (2018-09-07) 4
On 12/09/18 00:49, Stefan Beller wrote:
> 'calculate_changed_submodule_paths' uses a local list to compute the
> changed submodules, and then produces the result by copying appropriate
> items into the result list.
>
> Instead use the result list directly and prune items afterwards
> using
On 12/09/18 00:49, Stefan Beller wrote:
> Add a few functions to allow a string-list to be used as a stack:
>
> - string_list_last() lets a caller peek the string_list_item at the
>end of the string list. The caller needs to be aware that it is
>borrowing a pointer, which can become
On Tue, Sep 11, 2018 at 11:30 AM Ciro Santilli wrote:
> The mentioned --filter=tree:0 would basically do what I want it seems,
> good to hear!. I wonder why not call it tree:none though to match
> blob:none.
There are some plans of making tree: accept positive integers in order
to filter out
'calculate_changed_submodule_paths' uses a local list to compute the
changed submodules, and then produces the result by copying appropriate
items into the result list.
Instead use the result list directly and prune items afterwards
using string_list_remove_empty_items.
By doin so we'll have
Currently when git-fetch is asked to recurse into submodules, it dispatches
a plain "git-fetch -C " (and some submodule related options
such as prefix and recusing strategy, but) without any information of the
remote or the tip that should be fetched.
This works surprisingly well in some
We can string_list_insert() to maintain sorted-ness of the
list as we find new items, or we can string_list_append() to
build an unsorted list and sort it at the end just once.
To pick which one is more appropriate, we notice the fact
that we discover new items more or less in the already
sorted
This patch started as a refactoring to make 'get_next_submodule' more
readable, but upon doing so, I realized that git-fetch actually doesn't
need to be run in the worktree. So let's run it in the git dir instead.
That should pave the way towards fetching submodules that are currently
not checked
Add a few functions to allow a string-list to be used as a stack:
- string_list_last() lets a caller peek the string_list_item at the
end of the string list. The caller needs to be aware that it is
borrowing a pointer, which can become invalid if/when the
string_list is resized.
-
Currently when git-fetch is asked to recurse into submodules, it dispatches
a plain "git-fetch -C " (and some submodule related options
such as prefix and recusing strategy, but) without any information of the
remote or the tip that should be fetched.
This works surprisingly well in some
For Gerrit users that use submodules the invocation of fetch without a
branch is their main use case.
Signed-off-by: Stefan Beller
---
builtin/fetch.c | 5 -
t/t5526-fetch-submodules.sh | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/builtin/fetch.c
The `changed_submodule_names` are only used for fetching, so let's make it
part of the struct that is passed around for fetching submodules.
Signed-off-by: Stefan Beller
---
submodule.c | 42 +++---
1 file changed, 23 insertions(+), 19 deletions(-)
diff
Helped-by: Junio C Hamano
Signed-off-by: Stefan Beller
---
sha1-array.c | 18 ++
sha1-array.h | 5 +
2 files changed, 23 insertions(+)
diff --git a/sha1-array.c b/sha1-array.c
index 265941fbf40..76323935dd7 100644
--- a/sha1-array.c
+++ b/sha1-array.c
@@ -77,3 +77,21 @@
The submodule subsystem is really bad at staying within 80 characters.
Fix it while we are here.
Signed-off-by: Stefan Beller
---
submodule.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/submodule.c b/submodule.c
index a2b266fbfae..d29dfa3d1f5 100644
---
This patch helps address the CPU cost of loading the index by loading
the cache extensions on a worker thread in parallel with loading the cache
entries.
In some cases, loading the extensions takes longer than loading the
cache entries so this patch utilizes the new EOIE to start the thread to
The End of Index Entry (EOIE) is used to locate the end of the variable
length index entries and the beginning of the extensions. Code can take
advantage of this to quickly locate the index extensions without having
to parse through all of the index entries.
Because it must be able to be loaded
This version of the patch merges in Duy's work to speed up index v4 decoding.
I had to massage it a bit to get it to work with the multi-threading but its
still largely his code. It helps a little (3%-4%) when the cache entry thread(s)
take the longest and not when the index extensions loading is
This patch does a clean up pass to minimize the casting required to work
with the memory mapped index (mmap).
It also makes the decoding of network byte order more consistent by using
get_be32() where possible.
Signed-off-by: Ben Peart
---
read-cache.c | 49
From: Nguyễn Thái Ngọc Duy
Index format v4 requires some more computation to assemble a path
based on a previous one. The current code is not very efficient
because
- it doubles memory copy, we assemble the final path in a temporary
first before putting it back to a cache_entry
-
This patch helps address the CPU cost of loading the index by creating
multiple threads to divide the work of loading and converting the cache
entries across all available CPU cores.
It accomplishes this by having the primary thread loop across the index file
tracking the offset and (for V4
On Fri, Sep 7, 2018 at 5:35 PM Jonathan Nieder wrote:
>
> Hi,
>
> Thomas Braun wrote:
>
> > I'm using git with stash and rebase builtins.
> >
> > $ git --version --build-options
> >
> > git version 2.19.0.rc2.windows.1
> [...]
> > mkdir test
> > cd test
> > git init
> > echo 1 > file
> > git add
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'. The ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
Git 2.19 is out. The tip of
On Tue, Sep 11, 2018 at 4:26 PM Derrick Stolee via GitGitGadget
wrote:
> The commit 40ce4160 "format-patch: allow --range-diff to apply to
> a lone-patch" added the ability to see a range-diff as commentary
> after the commit message of a single patch series (i.e. [PATCH]
> instead of [PATCH
On Tue, Sep 11, 2018 at 4:26 PM Derrick Stolee via GitGitGadget
wrote:
> In es/format-patch-rangediff, we added a '--range-diff' option to
> git-format-patch to automatically add a range-diff. We also added an option
> to write the diff as commentary to a single patch submission. However, this
>
Junio C Hamano writes:
>> +test_expect_success 'format-patch --range-diff as commentary' '
>> +git format-patch --stdout --range-diff=HEAD~1 HEAD~1 >actual &&
>> +grep -A 1 -e "\-\-\-" actual | grep "Range-diff:"
>
> Isn't "grep -A" GNUism?
Sorry for short-write(2) X-<.
Perhaps
On Tue, Sep 11, 2018 at 1:21 PM Derrick Stolee via GitGitGadget
wrote:
>
> From: Derrick Stolee
>
> The commit 40ce4160 "format-patch: allow --range-diff to apply to
> a lone-patch" added the ability to see a range-diff as commentary
> after the commit message of a single patch series (i.e.
On Mon, Sep 10, 2018 at 08:08:35PM -0700, Stefan Beller wrote:
> > So the choice being offered are:
> >
> > (0) take 2/2 only, keeping zero unused helper.
> > (1) take 1/2 only, keeping two unused helpers.
> > (2) do nothing, keeping the simple unused helper we had from the
> > beginning
"Derrick Stolee via GitGitGadget" writes:
> From: Derrick Stolee
>
> The commit 40ce4160 "format-patch: allow --range-diff to apply to
> a lone-patch" added the ability to see a range-diff as commentary
> after the commit message of a single patch series (i.e. [PATCH]
> instead of [PATCH X/N]).
On Tue, Sep 11, 2018 at 01:36:01PM -0700, Junio C Hamano wrote:
> Jeff King writes:
>
> > I think that's syntactically invalid. At any rate, there are clearly
> > three options for setting a bit:
> >
> > 1. In the section header (+include, or Ævar's includeIf suggestion).
> >
> > 2. In
Stefan Beller writes:
>> >>
>> >> [1]
>> >> https://public-inbox.org/git/1421343725-3973-1-git-send-email-kuleshovm...@gmail.com/
>> >> Signed-off-by: Stefan Beller
>> >
>> > I'll add a blank line before the sign-off. Is this an example that
>> > our "where is the existing trailer?" code
Elijah Newren writes:
> check_one_conflict() compares `i` to `active_nr` in two places to avoid
> buffer overruns, but left out an important third location.
>
> The code did used to have a check here comparing i to active_nr, back
> before commit fb70a06da2f1 ("rerere: fix an off-by-one
Jeff King writes:
> I think that's syntactically invalid. At any rate, there are clearly
> three options for setting a bit:
>
> 1. In the section header (+include, or Ævar's includeIf suggestion).
>
> 2. In another key (which looks pretty clean, but does introduce
> ordering
This is a test of smart HTTP, so it should use the smart HTTP endpoints
(e.g. /info/refs?service=git-receive-pack), not dumb HTTP (HEAD).
Signed-off-by: Jonathan Nieder
Signed-off-by: Max Kirillov
---
> do you know why the test passes without 574c513e8d (http-backend: allow
> empty
On 9/11/2018 4:21 PM, Derrick Stolee via GitGitGadget wrote:
In es/format-patch-rangediff, we added a '--range-diff' option to
git-format-patch to automatically add a range-diff. We also added an option
to write the diff as commentary to a single patch submission. However, this
check was not
Ævar Arnfjörð Bjarmason writes:
> Based on feedback on v1, and the "this is yelling at my users through
> gc.log" bug I found.
I notice that between 'master' and 'pu' there already is one new
callsite of the write_commit_graph_reachable() function; because I
suspect that we will discover more
From: Derrick Stolee
The commit 40ce4160 "format-patch: allow --range-diff to apply to
a lone-patch" added the ability to see a range-diff as commentary
after the commit message of a single patch series (i.e. [PATCH]
instead of [PATCH X/N]). However, this functionality was not
covered by a test
In es/format-patch-rangediff, we added a '--range-diff' option to
git-format-patch to automatically add a range-diff. We also added an option
to write the diff as commentary to a single patch submission. However, this
check was not tested.
I discovered this test gap by running 'make coverage-test
From: Jeff Hostetler
Signed-off-by: Jeff Hostetler
---
compat/mingw.c| 36 ---
t/t0051-windows-named-pipe.sh | 2 +-
2 files changed, 34 insertions(+), 4 deletions(-)
diff --git a/compat/mingw.c b/compat/mingw.c
index 858ca14a57..18caf21969
The recent change mingw O_APPEND change breaks writing to named pipes on
Windows. The first commit adds a new test to confirm the breakage and the
second commit fixes the problem. These could be squashed together or we can
just keep the fix and omit the test if that would be better.
d641097589
From: Jeff Hostetler
Create a test-tool helper to create the server side of
a windows named pipe, wait for a client connection, and
copy data written to the pipe to stdout.
Create t0051 test to route GIT_TRACE output of a command
to a named pipe using the above test-tool helper.
Signed-off-by:
On Tue, Sep 11, 2018 at 9:54 PM Brad Davis wrote:
> I'm currently trying to determine when an issue was fixed in a long
> list of commits. I attempted to do this by running `git bisect` and
> marking the commit where I knew it was broken as bad, and the tip as
> good, but I got back an error
I'm currently trying to determine when an issue was fixed in a long
list of commits. I attempted to do this by running `git bisect` and
marking the commit where I knew it was broken as bad, and the tip as
good, but I got back an error message saying that good revs weren't
ancestors of bad ones.
Johannes Sixt writes:
>>> Like this (generated using "git revert -m1)?
>>
>> OK. Thanks for taking care of it.
>
> Please don't forget to remove the corresponding release notes entry.
Thanks for a reminder. Very much appreciated.
On Tue, Sep 11, 2018 at 12:31 PM Junio C Hamano wrote:
>
> Junio C Hamano writes:
>
> > Stefan Beller writes:
> >
> >> The helper function stayed unused for 3 years. A removal of that function
> >
> > I think it stayed unused for more than that before the previous
> > proposal to remove it was
Junio C Hamano writes:
> Stefan Beller writes:
>
>> The helper function stayed unused for 3 years. A removal of that function
>
> I think it stayed unused for more than that before the previous
> proposal to remove it was written (I do not bother going back to my
> earlier message that
Stefan Beller writes:
> The helper function stayed unused for 3 years. A removal of that function
I think it stayed unused for more than that before the previous
proposal to remove it was written (I do not bother going back to my
earlier message that identified which exact commit this was
Stefan Beller writes:
> On Tue, Sep 11, 2018 at 11:16 AM Junio C Hamano wrote:
>>
>> Stefan Beller writes:
>>
>> >> [...] So this should be sufficient.
>> >
>> > Yup.
>> > Thanks for keeping track of this patch, as I lost track of it.
>> >
>> > thanks,
>> > Stefan
>>
>> So does the above
On Tue, Sep 11, 2018 at 12:43:15PM +0200, Michal Novotny wrote:
> I need to emulate git tag --merged with very old git 1.8.3.1. Is that
> somehow possible?
> I am looking for a bash function that would take what git 1.8.3.1
> offers and return only the tags accessible from the current branch
>
This series documents and fixes a rerere segfault (dating back to
git-2.7.0) when a merge strategy makes the last entry in the index be
at stage 1.
Changes since last version:
- In my last submission I only had the code fix and no testcase; I
even commented in the commit message that the
Signed-off-by: Elijah Newren
---
t/t4200-rerere.sh | 29 +
1 file changed, 29 insertions(+)
diff --git a/t/t4200-rerere.sh b/t/t4200-rerere.sh
index 65da74c766..f9294b7677 100755
--- a/t/t4200-rerere.sh
+++ b/t/t4200-rerere.sh
@@ -577,4 +577,33 @@ test_expect_success
check_one_conflict() compares `i` to `active_nr` in two places to avoid
buffer overruns, but left out an important third location.
The code did used to have a check here comparing i to active_nr, back
before commit fb70a06da2f1 ("rerere: fix an off-by-one non-bug",
2015-06-28), however the code
The helper function stayed unused for 3 years. A removal of that function
was proposed before[1], but now time has proven we really do not need the
function.
[1]
https://public-inbox.org/git/1421343725-3973-1-git-send-email-kuleshovm...@gmail.com/
Signed-off-by: Stefan Beller
---
string-list.c
On Tue, Sep 11, 2018 at 11:16 AM Junio C Hamano wrote:
>
> Stefan Beller writes:
>
> >> [...] So this should be sufficient.
> >
> > Yup.
> > Thanks for keeping track of this patch, as I lost track of it.
> >
> > thanks,
> > Stefan
>
> So does the above exchange mean that
>
On Thu, Sep 6, 2018 at 11:03 AM Junio C Hamano wrote:
>
> Stefan Beller writes:
>
> > Instead of sorting it after we created an unsorted list, we could insert
> > correctly into the list.
>
> It is unclear what problem you are solving, especially with
> subjunctive "could" there. We are
On Tue, Sep 11, 2018 at 6:47 PM Junio C Hamano wrote:
>
> Jonathan Tan writes:
>
> > By "without any objects" in your email subject, do you mean "without
> > blob and tree objects"? If yes, there is some code in the
> > md/filter-trees branch that can do that with a "--filter=tree:0"
> > option.
Junio C Hamano writes:
>>> + /*
>>> +* According to RFC 3875, an empty or missing
>>> +* CONTENT_LENGTH means "no body", but RFC 3875
>>> +* precedes HTTP/1.1 and chunked encoding. Apache and
>>> +* its imitators leave CONTENT_LENGTH
Stefan Beller writes:
>> [...] So this should be sufficient.
>
> Yup.
> Thanks for keeping track of this patch, as I lost track of it.
>
> thanks,
> Stefan
So does the above exchange mean that
<20180904135258.31300-1-phillip.w...@talktalk.net> is ready to go
with your Acked-by?
Jonathan Nieder writes:
> Kicking off the reviews: ;-)
>
> Jonathan Nieder wrote:
>
>> --- a/http-backend.c
>> +++ b/http-backend.c
>> @@ -350,10 +350,25 @@ static ssize_t read_request_fixed_len(int fd, ssize_t
>> req_len, unsigned char **o
>>
>> static ssize_t get_content_length(void)
>
> [...] So this should be sufficient.
Yup.
Thanks for keeping track of this patch, as I lost track of it.
thanks,
Stefan
Jonathan Tan writes:
> By "without any objects" in your email subject, do you mean "without
> blob and tree objects"? If yes, there is some code in the
> md/filter-trees branch that can do that with a "--filter=tree:0"
> option.
I too was wondering what the "without any objects" thing meant
Todd Zullinger writes:
> With curl-7.61.1 cookies are sorted by creation-time¹. Sort the output
> used in the 'cookies stored in http.cookiefile when http.savecookies
> set' test before comparing it to the expected cookies.
>
> ¹ https://github.com/curl/curl/commit/e2ef8d6fa ("cookies: support
On 09/11, Thomas Gummerer wrote:
> I think you're on the right track here. I can not test this on Mac
> OS, but on Linux, the following fails when running the test under
> valgrind:
>
> diff --git a/t/t3206-range-diff.sh b/t/t3206-range-diff.sh
> index 2237c7f4af..a8b0ef8c1d 100755
>
"Stephen P. Smith" writes:
> On Friday, September 7, 2018 3:31:55 PM MST you wrote:
>> Junio C Hamano writes:
>
>> The patch is mostly for illustration of the idea.
>>
>> The result seems to compile and pass the test suite, but I haven't
>> carefully thought about what else I may be breaking
On Tue, Sep 11, 2018 at 10:15 AM, Stefan Beller wrote:
> You might be pleased to hear about a series floating on the mailing list,
> that started at
> https://public-inbox.org/git/cover.1533854545.git.matv...@google.com/
> and promised to filter trees away, and its latest version can be found at
On Tue, Sep 11, 2018 at 12:29 AM Ciro Santilli wrote:
>
> At v2.19.0 I was trying to clone a fetch just a single directory:
> https://stackoverflow.com/questions/600079/how-do-i-clone-a-subdirectory-only-of-a-git-repository/52269934#52269934
>
> I got really close with:
>
> git clone --depth 1
Duy Nguyen writes:
> In the end, there's no variant, only one function that always takes
> 'struct repository *' and I wanted to keep the shorter name 'rerere'.
> But let's go with adding repo_rerere() and deprecating rerere(). If it
> turns out later that repo_rerere is too long (or it's
Nguyễn Thái Ngọc Duy writes:
> ---
> apply.c| 9 ++---
> builtin/checkout.c | 3 ++-
> diff.c | 2 +-
> ll-merge.c | 17 +
> ll-merge.h | 5 -
> merge-blobs.c | 3 ++-
> merge-recursive.c | 3 ++-
> notes-merge.c
Derrick Stolee writes:
> On 9/11/2018 12:04 PM, Derrick Stolee wrote:
>
>> The patch below includes a test that fails on Mac OSX with a segfault.
> ...
> Sorry, nevermind. The test failed for a different reason:
Even if it is for a different reason, segfaulting is not acceptable,
but it seems
On Tue, Sep 11, 2018 at 9:07 AM ryenus wrote:
> On Tue, 11 Sep 2018 at 23:49, Thomas Gummerer wrote:
> >
> > Hi,
> >
> > thanks for your bug report!
> >
> > On 09/11, ryenus wrote:
> > > I just updated to 2.19 via Homebrew, git range-diff seems cool, but I
> > > only got a Segmentation fault: 11
On 09/11, Derrick Stolee wrote:
> On 9/11/2018 12:04 PM, Derrick Stolee wrote:
> > On 9/11/2018 11:38 AM, Derrick Stolee wrote:
> > The patch below includes a test that fails on Mac OSX with a segfault.
> >
> > GitGitGadget PR: https://github.com/gitgitgadget/git/pull/36
> > Failed Build:
> >
Hi,
If you have photos for editing, please send email to: hansre...@outlook.com
We have 12 in house image editors and we can help you for cutting out your
photos, or path the photos.
Includes retouching if needed.
Used for products photos or portrait photos, catalog photos.
You may drop us
On 9/11/2018 12:04 PM, Derrick Stolee wrote:
On 9/11/2018 11:38 AM, Derrick Stolee wrote:
On 9/11/2018 11:25 AM, ryenus wrote:
I just updated to 2.19 via Homebrew, git range-diff seems cool, but I
only got a Segmentation fault: 11
$ git version; git range-diff origin/master HEAD@{2}
On Mon, Sep 10, 2018 at 12:27 PM Hultqvist wrote:
>
> Sending again without HTML
>
> Den mån 10 sep. 2018 kl 12:28 skrev Hultqvist :
> >
> > First I need to correct my previous observations.
Please don't top-post.
> > Today there appeared new set of config files in the root.
> > I looked into a
On Mon, Sep 10, 2018 at 8:50 PM Stefan Beller wrote:
>
> On Sun, Sep 9, 2018 at 1:54 AM Nguyễn Thái Ngọc Duy wrote:
> >
> > ---
>
> Junio would have to forge your Sign off here?
I _knew_ I missed something in that "git format-patch" command but
couldn't figure out what! Will resend (I have to
On 9/11/2018 11:38 AM, Derrick Stolee wrote:
On 9/11/2018 11:25 AM, ryenus wrote:
I just updated to 2.19 via Homebrew, git range-diff seems cool, but I
only got a Segmentation fault: 11
$ git version; git range-diff origin/master HEAD@{2} HEAD
git version 2.19.0
Segmentation
On Tue, 11 Sep 2018 at 23:49, Thomas Gummerer wrote:
>
> Hi,
>
> thanks for your bug report!
>
> On 09/11, ryenus wrote:
> > I just updated to 2.19 via Homebrew, git range-diff seems cool, but I
> > only got a Segmentation fault: 11
> >
> > $ git version; git range-diff origin/master
On Tue, Sep 11, 2018 at 2:55 PM Jean-Noël Avila wrote:
>
> Hi,
>
>
> When invoking the autocompletion help with after a double
> hyphen under zsh, the help list is not localized. I guess the help list
> comes from some usage output of the on-going git command, but I wasn't
> able to find where
Hi,
If you have photos for editing, please send email to: hansre...@outlook.com
We have 12 in house image editors and we can help you for cutting out your
photos, or path the photos.
Includes retouching if needed.
Used for products photos or portrait photos, catalog photos.
You may drop us
Hi,
thanks for your bug report!
On 09/11, ryenus wrote:
> I just updated to 2.19 via Homebrew, git range-diff seems cool, but I
> only got a Segmentation fault: 11
>
> $ git version; git range-diff origin/master HEAD@{2} HEAD
Unfortunately the HEAD@{2} syntax needs your reflog, which is
On Tue, Sep 11, 2018 at 8:27 AM ryenus wrote:
>
> I just updated to 2.19 via Homebrew, git range-diff seems cool, but I
> only got a Segmentation fault: 11
>
> $ git version; git range-diff origin/master HEAD@{2} HEAD
> git version 2.19.0
> Segmentation fault: 11
>
> Both
On 9/11/2018 11:25 AM, ryenus wrote:
I just updated to 2.19 via Homebrew, git range-diff seems cool, but I
only got a Segmentation fault: 11
$ git version; git range-diff origin/master HEAD@{2} HEAD
git version 2.19.0
Segmentation fault: 11
Both origin/master and my local
I just updated to 2.19 via Homebrew, git range-diff seems cool, but I
only got a Segmentation fault: 11
$ git version; git range-diff origin/master HEAD@{2} HEAD
git version 2.19.0
Segmentation fault: 11
Both origin/master and my local branch each got two new commits of their own,
On Tue, Sep 11, 2018 at 1:19 PM, Derrick Stolee wrote:
> On 9/11/2018 1:22 AM, Christian Couder wrote:
>> It would be nice if the "Future Work" section of
>> Documentation/technical/commit-graph.txt had something about
>> integration with 'git gc'.
>
> I'm a bit confused about this statement,
On 9/10/2018 6:00 PM, Junio C Hamano wrote:
Johannes Sixt writes:
+#define IS_SBS(ch) (((ch) == '/') || ((ch) == '\\'))
I think you already have mingw_is_dir_sep() and its shorter alias
is_dir_sep() available to you.
good catch. thanks.
+/*
+ * Does the pathname map to the local
Hi,
When invoking the autocompletion help with after a double
hyphen under zsh, the help list is not localized. I guess the help list
comes from some usage output of the on-going git command, but I wasn't
able to find where and how this happens (completion scripts are quite
hairy).
Thanks
On 9/11/2018 1:22 AM, Christian Couder wrote:
On Wed, Jun 27, 2018 at 3:24 PM, Derrick Stolee wrote:
When writing commit-graph files, it can be convenient to ask for all
reachable commits (starting at the ref set) in the resulting file. This
is particularly helpful when writing to stdin is
Hello,
My name is ms. Reem Al-Hashimi. The UAE minister of state for international
cooparation. I got your contact from a certain email database from your country
while i was looking for someone to handle a huge financial transaction for me
in confidence. Can you receive and invest on behalf
Hello,
I need to emulate git tag --merged with very old git 1.8.3.1. Is that
somehow possible?
I am looking for a bash function that would take what git 1.8.3.1
offers and return only the tags accessible from the current branch
tip. Could you, please, give me at least a hint how this could be
On 04/09/2018 19:51, Phillip Wood wrote:
> Hi Stefan
>
> On 04/09/2018 19:08, Stefan Beller wrote:
>> On Tue, Sep 4, 2018 at 6:53 AM Phillip Wood
>> wrote:
>>>
>>> From: Phillip Wood
>>>
>>> If there is more than one potential moved block and the longest block
>>> is not the first element of
PS: while I was trying to send the mail to this mailing list, there is
some update from the stack overflow side:
* I am using sslBackend schannel
* the private key of my client certificate can be provided by using
the http.sslKey config option
* the private key is on a smart card, so there is no
no, using SSH is not an option. I have no control over the server
setup whatsoever.
Thx!
On Mon, Sep 10, 2018 at 3:29 PM, Randall S. Becker
wrote:
> On September 10, 2018 4:09 AM, Sergei Haller wrote:
>> my problem is basically the following: my git server (https) requires
>> authentication
At v2.19.0 I was trying to clone a fetch just a single directory:
https://stackoverflow.com/questions/600079/how-do-i-clone-a-subdirectory-only-of-a-git-repository/52269934#52269934
I got really close with:
git clone --depth 1 --no-checkout --filter=blob:none \
"file://$(pwd)/server_repo"
100 matches
Mail list logo
