Hey jch!
I'll change the signature of the function in next revision.
Thanks
Rohit
Hey Peff!
On 2019-04-13 1:34 UTC Jeff King wrote:
> What is gzwrite()?
> [...]
> I think it would be less confusing if this just factored out
> write_block_or_die(), which starts as a thin wrapper and then grows the
> gzip parts in the next patch.
You are right, it might appear to someone as a
Christian Couder writes:
> I can send a new version where the top two commits have the following titles:
>
> - replace: peel tag when passing a tag first to --graft
> - replace: peel tag when passing a tag as parent to --graft
If/when there are other things that needs fixing in the series, t
Barret Rhoden writes:
> This replaces the heuristic used to identify lines from ignored commits
> with one that finds likely candidate lines in the parent's version of
> the file.
>
> The old heuristic simply assigned lines in the target to the same line
> number (plus offset) in the parent. The
Barret Rhoden writes:
> Sometimes we are unable to even guess at what commit touched a line.
> These lines are 'unblamable.' The second option,
> blame.maskIgnoredUnblamables, will zero the hash of any unblamable line.
>
> For example, say we ignore e5e8d36d04cbe:
> e5e8d36d04cbe (Barret R
"Johannes Schindelin via GitGitGadget"
writes:
> + disallow_abbreviated_options =
> + git_env_bool("GIT_TEST_DISALLOW_ABBREVIATED_OPTIONS", 0);
... which means that the value of the environment variable follows
the usual "true, yes and 1 all activate it"; very good,
> diff --git
Thanks for the info about the upcoming "precious" attribute. Looks useful.
I didn't get the impression that Git normally overwrites ignored
files. I ran some more experiments:
git rebase FETCH_HEAD# bails
git rebase -i FETCH_HEAD # overwrites
git merge FETCH_HEAD # bails
git r
In 7a36987fff ("send-email: add an auto option for transfer encoding",
2018-07-08), git send-email learned how to automatically determine the
transfer encoding for a patch. However, the only criterion considered
was the length of the lines.
Another case we need to consider is that of carriage retu
On Fri, Apr 12, 2019 at 09:51:02PM -0400, Jeff King wrote:
> I wondered how you were going to kick this in, since users can define
> arbitrary filters. I think it's kind of neat to automagically convert
> "gzip -cn" (which also happens to be the default). But I think we should
> mention that in the
Am 13.04.2019 um 03:51 schrieb Jeff King:
> On Fri, Apr 12, 2019 at 04:04:40PM -0700, Rohit Ashiwal via GitGitGadget
> wrote:
>
>> From: Rohit Ashiwal
>>
>> As we already link to the zlib library, we can perform the compression
>> without even requiring gzip on the host machine.
>
> Very cool. It
On Sat, Apr 13, 2019 at 10:39:35PM +0200, Ævar Arnfjörð Bjarmason wrote:
>
> On Sat, Apr 13 2019, Randall S. Becker wrote:
>
> > I am encountering a problem on one of our NonStop platform variants where
> > the GIT_SSH_COMMAND string is not being broken into constituent parts. This
> > is causing
On Sat, Apr 06 2019, Denton Liu wrote:
> On Sat, Apr 06, 2019 at 09:44:49PM +0200, Ævar Arnfjörð Bjarmason wrote:
>>
>> On Mon, Apr 01 2019, Denton Liu wrote:
>>
>> > Thanks again for your feedback, Ævar! I think we're both on the same page
>> > now.
>> > Hopefully I've addressed all of your hi
On April 13, 2019 16:40, Ævar Arnfjörð Bjarmason wrote:
> On Sat, Apr 13 2019, Randall S. Becker wrote:
>
> > I am encountering a problem on one of our NonStop platform variants
> > where the GIT_SSH_COMMAND string is not being broken into constituent
> > parts. This is causing SSH to not run prop
On Sat, Apr 13 2019, Randall S. Becker wrote:
> I am encountering a problem on one of our NonStop platform variants where
> the GIT_SSH_COMMAND string is not being broken into constituent parts. This
> is causing SSH to not run properly. As background, SSH is not in a standard
> location and has
I am encountering a problem on one of our NonStop platform variants where
the GIT_SSH_COMMAND string is not being broken into constituent parts. This
is causing SSH to not run properly. As background, SSH is not in a standard
location and has non-standard required arguments. This also occurs with
c
On Sat, 13 Apr 2019 at 07:32, Mgr Georg Black wrote:
> People from big company(BC) wanna to have only one big repository with all
> code in it. BC wanna have to folders structure for language and projects. But
> for us is that idea bit uncomfortable because we rather have more
> repositories by
From: Torsten Bögershausen
Currently the length of data which is stored in memory is stored
in "unsigned long" at many places in the code base.
This is OK when both "unsigned long" and size_t are 32 bits,
(and is OK when both are 64 bits).
On a 64 bit Windows system am "unsigned long" is 32 bit,
On Sat, Apr 13, 2019 at 7:14 PM SZEDER Gábor wrote:
>
> On Fri, Apr 12, 2019 at 04:25:08PM +0200, Johannes Schindelin wrote:
> > Hi,
> >
> > On Fri, 12 Apr 2019, SZEDER Gábor wrote:
> >
> > > On Thu, Apr 11, 2019 at 10:58:57PM +0200, SZEDER Gábor wrote:
> > > > On Thu, Apr 11, 2019 at 10:51:46PM +
On Sat, Apr 13, 2019 at 05:16:00PM +0700, Nguyễn Thái Ngọc Duy wrote:
> OK how about this? set_commit_tree() is added to keeps that long line
> in commit.cocci down. I also make commit.cocci generate invalid
> repo_get_commit_tree() code this time.
> diff --git a/contrib/coccinelle/commit.cocci
On Fri, Apr 12, 2019 at 04:25:08PM +0200, Johannes Schindelin wrote:
> Hi,
>
> On Fri, 12 Apr 2019, SZEDER Gábor wrote:
>
> > On Thu, Apr 11, 2019 at 10:58:57PM +0200, SZEDER Gábor wrote:
> > > On Thu, Apr 11, 2019 at 10:51:46PM +0200, SZEDER Gábor wrote:
> > > > On Wed, Apr 10, 2019 at 10:56:52P
On Fri, Apr 12, 2019 at 12:14 PM Junio C Hamano wrote:
> > - git-rm learns about --staged as an alias of --cached (in fact it's
> > more the other way around). This is to keep suggestions consistent
> > because we tell people to do "git foo --staged" everywhere.
>
> I am not sure 100% about th
I've had enough. Please drop this nd/precious. I'm not updating it anymore.
On Sat, Apr 13, 2019 at 4:54 AM Ævar Arnfjörð Bjarmason
wrote:
>
>
> On Tue, Apr 09 2019, Nguyễn Thái Ngọc Duy wrote:
>
> > Here's the replacement patch that keeps "git clean" behavior the same
> > as before and only ch
Remove the implicit dependency on the_repository in this function.
It will be used in sha1-name.c functions when they are updated to take
any 'struct repository'. get_commit_tree() remains as a compat wrapper,
to be slowly replaced later.
set_commit_tree() is added just to simplify the filtering i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
I did a deep analysis of the problem and found that the trouble finally
was caused of some change in git (I did not search, when this changed.
But maybe you can tell me.)
Finally, the error was a combination of 4 tools, git, vim, the mentioned
On Fri, 12 Apr 2019 at 12:39, Johannes Schindelin via GitGitGadget
wrote:
>
> From: Johannes Schindelin
>
> Most notably, it seems that macOS' APFS does not allow that.
Did you mean in the subject "ISO-8895-1" encoded or "ISO-8859-1" encoded?
It seems reasonable other than that!
>
> Signed-off
25 matches
Mail list logo
