Johannes Schindelin writes:
> The only problem is that my patch made it into `next` already, according
> to https://github.com/gitgitgadget/git/pull/129 (look for the labels on
> the right side, or for the comments on the bottom), and
> https://github.com/gitster/git/commit/a3f332f4fb10 agrees (l
"Alexandr Miloslavskiy via GitGitGadget"
writes:
> From: Alexandr Miloslavskiy
>
> After I discovered that UTF-16-LE-BOM test was bugged, I decided that
s/bugged/buggy/ perhaps? Usually people do not place hidden
listening devices in tests ;-)
> better tests are required. Possibly the best op
On Sat, Sep 28, 2019 at 12:24 AM Junio C Hamano wrote:
>
> Matheus Tavares Bernardino writes:
>
> > Right, this would be the best way of doing it. However, I think this
> > is not how it's currently implemented. I if correctly understood the
> > code in this call chain:
> >
> > grep_source_load_d
SZEDER Gábor writes:
>> Hmm...
>>
>> > +# ,---ooo-.
>> > +# / D,R e \
>> > +# o--o-o-o---ox
>> > +# \B/
>> > +# `---ooo-'
>> > +#Ac
>>
>> What's the first parent of the merge between
Eric Wong writes:
> C is fine for unit tests, and maybe we can use more unit tests
> and less integration tests.
Nicely put. I often find it somewhat disturbing that what some of
the t/helper/ tests are trying to exercise is at too low a level
that the distance from the real-world observable ef
Jeff King writes:
> On Tue, Sep 24, 2019 at 04:25:45PM +0200, Johannes Schindelin wrote:
>
>> > I think it could make sense for merge-index to be able to directly run
>> > the merge-one-file code[1]. But I think we'd want to keep its ability to
>> > run an arbitrary script, and for people to call
William Baker writes:
> On 9/20/19 1:10 PM, Junio C Hamano wrote:
>>> diff --git a/midx.c b/midx.c
>>> index b2673f52e8..54e4e93b2b 100644
>>> --- a/midx.c
>>> +++ b/midx.c
>>> @@ -449,6 +449,8 @@ struct pack_list {
>>> uint32_t nr;
>>> uint32_t alloc;
>>> struct multi_pack_index *m;
SZEDER Gábor writes:
> On Fri, Sep 20, 2019 at 09:53:48AM -0700, William Baker via GitGitGadget
> wrote:
>> diff --git a/midx.h b/midx.h
>> index f0ae656b5d..e6fa356b5c 100644
>> --- a/midx.h
>> +++ b/midx.h
>> @@ -37,6 +37,8 @@ struct multi_pack_index {
>> char object_dir[FLEX_ARRAY];
>>
Matheus Tavares Bernardino writes:
> Right, this would be the best way of doing it. However, I think this
> is not how it's currently implemented. I if correctly understood the
> code in this call chain:
>
> grep_source_load_driver() > userdiff_find_by_path() >
> git_check_attr() > collect_some_
Brauchen Sie dringend einen Kredit fur geschaftliche und private
Angelegenheiten? Ich bin ein privater Kreditgeber und kann Ihren Kredit
finanzieren. Ich gebe alle Arten von Darlehen zu einem gunstigen Zinssatz aus.
Solange Sie das Darlehen zuruckzahlen konnen, ist keine Bonitatsprufung
erfo
On 2019-09-27 at 12:55:27, Ian Kemp wrote:
> Hi,
>
> Currently, git stash's exit code is 0 regardless of whether it
> performed a stash operation or not. Third parties invoking git stash
> are therefore unable to determine whether a stash was actually made or
> not.
>
> It would be helpful if the
On Thu, Sep 26, 2019 at 11:44:48PM +0200, SZEDER Gábor wrote:
> All that was over a year and a half ago, and these limitations weren't
> a maintenance burden at all so far, and nobody needed that escape
> hatch.
>
> Well, nobody except me, that is :) When I saw back then that t1510
> saves the s
On Wed, Sep 25, 2019 at 05:33:00PM -0700, Jonathan Tan wrote:
> Does anyone have ideas or plans for this? I know that (at least) "grep"
> and "index-pack" have their own implementations, and it would be great
> to just have one that all code can use.
> [..]
> Searching reveals [2], but I don't thi
On 26/09/2019 08:20, Jeff King wrote:
> On Tue, Sep 24, 2019 at 04:52:56PM -0700, Emily Shaffer wrote:
>> I helped my other FOSS project to adopt a Code of Conduct earlier in
>> the year (https://github.com/openbmc/docs/blob/master/code-of-conduct.md)
>> and we got around this by asking for volunte
I was going to make a bug-report about this funny behavior, but
decided to search the list first.
Yeah, I smiled at
Expanding reachable commits in commit graph: 139276% (870481/625), done.
when I did the "git gc --prune=now" on the kernel, and apparently
actually looked at the noise for the
On Fri, Sep 27, 2019 at 04:17:46AM +0200, SZEDER Gábor wrote:
> On Fri, Sep 27, 2019 at 03:09:30AM +0200, SZEDER Gábor wrote:
> > On Wed, Sep 25, 2019 at 01:39:19PM -0700, Denton Liu wrote:
> > > Hi Elijah,
> > >
> > > I ran into a segfault on MacOS. I managed to bisect it down to
> > > 404ebceda0
On Fri, Sep 27, 2019 at 8:55 AM Ian Kemp wrote:
> Currently, git stash's exit code is 0 regardless of whether it
> performed a stash operation or not. Third parties invoking git stash
> are therefore unable to determine whether a stash was actually made or
> not.
>
> It would be helpful if there w
On 10.09.2019 08:13, Konstantin Ryabitsev wrote:
# Proposed approach
I recommend that we provide a way to include cryptographic signature
information natively using git-format-patch, using roughly the following
process:
- generate a signify-compatible cryptographic signature of the verbatim
pa
Hi Alban
On 25/09/2019 21:13, Alban Gruin wrote:
This can be seen as a continuation of ag/reduce-rewriting-todo.
Currently, complete_action() releases its todo list before calling
sequencer_continue(), which reloads the todo list from the disk. This
series removes this useless round trip.
Pat
--
Ahoj drahý
ako sa máš?
volám sa Edith Brownová
Som vojenská žena z USA
je mi potešením stretnúť sa tu
S Pozdravom
Hi Alban
On 25/09/2019 21:13, Alban Gruin wrote:
get_replay_opts() did not fill `squash_onto' if possible, meaning that
I'm not sure what you mean by 'if possible' here, I think the sentance
makes sense without that.
this field should be read from the disk by the sequencer through
read_pop
Hi Alban
Thanks for removing some more unnecessary work reloading the the todo list.
On 25/09/2019 21:13, Alban Gruin wrote:
Currently, complete_action() calls sequencer_continue() to do the
rebase. Even though the former already has the todo list, the latter
loads it from the disk and parses
On 27/09/19 08:10AM, Bert Wesarg wrote:
> On Fri, Sep 27, 2019 at 12:40 AM Pratyush Yadav
> wrote:
> >
> > Hi,
> >
> > On 26/09/19 02:17PM, Johannes Schindelin via GitGitGadget wrote:
> > > From: Johannes Schindelin
> > >
> > > Since v2.9.0, Git knows about the config variable core.hookspath
> >
Hi,
Currently, git stash's exit code is 0 regardless of whether it
performed a stash operation or not. Third parties invoking git stash
are therefore unable to determine whether a stash was actually made or
not.
It would be helpful if there were different exit codes for the case
when a stash was
On 9/27/2019 8:21 AM, Johannes Schindelin wrote:
> Hi,
>
>
> On Thu, 26 Sep 2019, Alex Henrie wrote:
>
>> Signed-off-by: Alex Henrie
>
> Hrm, the commit message should reflect Stolee's careful consideration,
> no? An empty commit message won't be helpful e.g. when cherry-picking on
> top of a
Hi,
On Thu, 26 Sep 2019, Alex Henrie wrote:
> Signed-off-by: Alex Henrie
Hrm, the commit message should reflect Stolee's careful consideration,
no? An empty commit message won't be helpful e.g. when cherry-picking on
top of a branch that already has your v1.
Ciao,
Johannes
> ---
> commit-gr
On Fri, Sep 27, 2019 at 11:51:07AM +0200, Anders Janmyr wrote:
> Hi,
>
> I'm not sure if this is a bug or not but `git describe` gives
> different results when the repo has been cloned with `--depth` or not.
>
> In the example below from the git repository the number of additional
> commits since
On 9/26/2019 10:45 PM, Jeff King wrote:
> On Tue, Sep 24, 2019 at 08:01:58PM -0600, Alex Henrie wrote:
>
>> diff --git a/wrapper.c b/wrapper.c
>> index c55d7722d7..c23ac6adcd 100644
>> --- a/wrapper.c
>> +++ b/wrapper.c
>> @@ -469,13 +469,12 @@ int git_mkstemps_mode(char *pattern, int suffix_len,
Hi Rohit
This is an improvement but there are a couple of outstanding issues from
the previous round with regard to handing --ignore-date when
GIT_COMMITTER_DATE is set. I'll try and look at the rest of the series soon.
On 07/09/2019 12:50, Rohit Ashiwal wrote:
rebase am already has this fla
Hi,
I'm not sure if this is a bug or not but `git describe` gives
different results when the repo has been cloned with `--depth` or not.
In the example below from the git repository the number of additional
commits since the
last tag differs 256 vs. 265.
```
$ git clone https://github.com/git/gi
On 09/27, Beyondhorizon Zheng wrote:
> [git issue] git am failed for patches of converting the file format of
> source codes from dos to unix
>
> Git version: git version 2.23.0
> Host PC: ubuntu 16.04.10
> Reporter: Shuang Zheng
>
> I have submitted a patch which convert the file format of sourc
[git issue] git am failed for patches of converting the file format of
source codes from dos to unix
Git version: git version 2.23.0
Host PC: ubuntu 16.04.10
Reporter: Shuang Zheng
I have submitted a patch which convert the file format of source file
from dos to unix with command:
dos2unix misc/a
32 matches
Mail list logo
