On Mon, Feb 4, 2019 at 9:41 PM brian m. carlson
wrote:
>
> On Mon, Feb 04, 2019 at 09:18:14PM -0500, Larry Martell wrote:
> > On Mon, Feb 4, 2019 at 9:15 PM brian m. carlson
> > wrote:
> > > If you want to generate a file, you can certainly do that in the
> > > post-commit hook or using a Makefil
On Mon, Feb 04, 2019 at 09:18:14PM -0500, Larry Martell wrote:
> On Mon, Feb 4, 2019 at 9:15 PM brian m. carlson
> wrote:
> > If you want to generate a file, you can certainly do that in the
> > post-commit hook or using a Makefile target. You just can't check it
> > into the repo. Lots of project
In order to enable greater user customisation of the SPARSE_FLAGS
variable, we introduce a new SP_EXTRA_FLAGS variable to use for
target specific settings. Without using the new variable, setting
the SPARSE_FLAGS on the 'make' command-line would also override the
value set by the target-specific
An upcoming commit will change the semantics of the SPARSE_FLAGS
variable from an internal to a user only customisation variable.
The MinGW configuration section contains an obsolete setting for
this variable which was used (some years ago) to cater to an error
in the Win32 system header files. S
Changes in v2:
- Add a new patch #1, which removes an obsolete use of SPARSE_FLAGS
- Actually initialise the new SP_EXTRA_FLAGS variable
- Reword the commit message (now #2) to, hopefully, clarify the
usage of SPARSE_FLAGS and SP_EXTRA_FLAGS
A range-diff against v1 is given at the ver
On Mon, Feb 4, 2019 at 9:15 PM brian m. carlson
wrote:
>
> On Mon, Feb 04, 2019 at 09:00:42PM -0500, Larry Martell wrote:
> > Thanks for the reply. Any suggestions on how to achieve what I want to do?
> >
> > The use case is that we want to have a file that is part of the
> > install that has cert
On Mon, Feb 04, 2019 at 09:00:42PM -0500, Larry Martell wrote:
> Thanks for the reply. Any suggestions on how to achieve what I want to do?
>
> The use case is that we want to have a file that is part of the
> install that has certain info (commit id, date of commit, commit
> message, etc.). and w
On Mon, Feb 4, 2019 at 8:55 PM brian m. carlson
wrote:
>
> On Mon, Feb 04, 2019 at 08:36:10PM -0500, Larry Martell wrote:
> > Is there any way using a git hook to get info on the commit (id,
> > message), put that in a file, and include that file in the commit?
> >
> > If I try that in a pre-commi
On Mon, Feb 04, 2019 at 08:36:10PM -0500, Larry Martell wrote:
> Is there any way using a git hook to get info on the commit (id,
> message), put that in a file, and include that file in the commit?
>
> If I try that in a pre-commit hook I do not get the info on the
> current commit. I tried it in
On Wed, Jan 30, 2019 at 10:06:05PM +0330, Alireza Alipour wrote:
> Hi everyone
>
> I have asked this question in Super User but I have not got answer. I
> have described details in the my question__ link in available in
> bottom__ but for more information I add following info:
>
> I checked one o
Is there any way using a git hook to get info on the commit (id,
message), put that in a file, and include that file in the commit?
If I try that in a pre-commit hook I do not get the info on the
current commit. I tried it in pre-receive but it does not seem to get
executed at all.
If I do it in
On February 4, 2019 12:10:54 p.m. CST, Junio C Hamano wrote:
>Duy Nguyen writes:
>
>>> The disadvantage, of course, would be that other call sites would
>not
>>> benefit from a manual auditing whether the argument has side effects
>(and
>>> thus, whether a macro using the argument multiple time
On Tue, Feb 05 2019, Jeff King wrote:
> On Mon, Feb 04, 2019 at 12:04:21PM -0800, Junio C Hamano wrote:
>
>> Instead of exposing this pretty-much "test-only" feature as a new
>> option to t/helper/test-tool, I think it is OK, if not even better,
>> to have it in rev-parse proper like this patch
On Mon, Feb 04, 2019 at 09:50:37PM +0100, Martin Ågren wrote:
> `usage` tries to call $0, which might very well be "./doc-diff", so if
> we `cd_to_toplevel` before calling `usage`, we'll end with an error to
> the effect of "./doc-diff: not found" rather than a friendly `doc-diff
> -h` output. Thi
On Mon, Feb 04, 2019 at 12:04:21PM -0800, Junio C Hamano wrote:
> Instead of exposing this pretty-much "test-only" feature as a new
> option to t/helper/test-tool, I think it is OK, if not even better,
> to have it in rev-parse proper like this patch does.
>
> I however have a mildly strong suspi
On Mon, Feb 04, 2019 at 01:45:35PM +, Luke Diamand wrote:
> I tried to do a partial clone, but it gave me a "bad pack header". Is
> there anything I can do to debug this?
>
> I did "git config uploadpack.allowfilter true" in my repo.
> Then I went to a scratch directory and did:
> $ git clone
Johannes Sixt writes:
> strbuf_vinsertf inserts a formatted string in the middle of an existing
> strbuf value. It makes room in the strbuf by moving existing string to
> the back, then formats the string to insert directly into the hole.
>
> It uses vsnprintf to format the string. The buffer siz
On 02/04, Christian Couder wrote:
> Hi everyone,
>
> There are now ideas, micro-projects and organization application pages
> for GSoC 2019 on https://git.github.io/
>
> It would be nice to have a few more project ideas.
> https://git.github.io/SoC-2019-Ideas/ currently lists only 2 possible
> pr
On Mon, Feb 04 2019, Junio C Hamano wrote:
> Ævar Arnfjörð Bjarmason writes:
>
>> ...::
>> If provided, the results are limited to a subset of files
>> -matching one of these prefix strings.
>> -i.e., file matches `/^||.../`
>> -Note that this parameter does not provide any w
On Mon, Feb 04 2019, Junio C Hamano wrote:
> Ævar Arnfjörð Bjarmason writes:
>
>> @@ -773,6 +773,14 @@ int cmd_rev_parse(int argc, const char **argv, const
>> char *prefix)
>> return 1;
>> continue;
>> }
>>
Thomas Gummerer writes:
> There was also some discussion around the naming of the option, but I
> don't have a strong opinion on that, so I'm happy with keeping the
> --[no-]overlay option. I just wanted to bring it up again here in
> case someone had a very strong opinion, and would prefer it b
Elijah Newren writes:
There is one place that says combined-all-paths, and everywhere else
it says combined-all-names. The former is probably techincally more
correct, I think ;-)
> The combined diff format for merges will only list one filename, even if
> rename or copy detection is active. F
Am 04.02.19 um 11:38 schrieb Johannes Schindelin:
> On Mon, 4 Feb 2019, Johannes Sixt wrote:
>
>> Am 03.02.19 um 17:51 schrieb Johannes Sixt:
>>> strbuf_vinsertf inserts a formatted string in the middle of an existing
>>> strbuf value.
>>
>> Quite frankly, this is a really unusual operation, and I
On 01/29, Junio C Hamano wrote:
> * tg/checkout-no-overlay (2019-01-08) 8 commits
> (merged to 'next' on 2019-01-18 at 1e2a79ba5c)
> + checkout: introduce checkout.overlayMode config
> + checkout: introduce --{,no-}overlay option
> + checkout: factor out mark_cache_entry_for_checkout function
Ævar Arnfjörð Bjarmason writes:
> ...::
> If provided, the results are limited to a subset of files
> - matching one of these prefix strings.
> - i.e., file matches `/^||.../`
> - Note that this parameter does not provide any wildcard or regexp
> - features.
> + matchi
`usage` tries to call $0, which might very well be "./doc-diff", so if
we `cd_to_toplevel` before calling `usage`, we'll end with an error to
the effect of "./doc-diff: not found" rather than a friendly `doc-diff
-h` output. This regressed in ad51743007 ("doc-diff: add --clean mode to
remove tempor
On 04/02/2019 20:15, Junio C Hamano wrote:
> Ramsay Jones writes:
>
>> On 04/02/2019 18:12, Junio C Hamano wrote:
>>> Ramsay Jones writes:
>>>
> Thanks for a detailed and clear explanation here and in the cover
> letter. I agree with the motivation and most of the things I see in
>>>
Ramsay Jones writes:
> On 04/02/2019 18:12, Junio C Hamano wrote:
>> Ramsay Jones writes:
>>
Thanks for a detailed and clear explanation here and in the cover
letter. I agree with the motivation and most of the things I see in
this patch, but one thing that stands out at me is i
The combined diff format for merges will only list one filename, even if
rename or copy detection is active. For example, with raw format one
might see:
::100644 100644 100644 fabadb8 cc95eb0 4866510 MM describe.c
::100755 100755 100755 52b7a2d 6d1ac04 d2ac7d7 RM bar.sh
::100644 100
Ævar Arnfjörð Bjarmason writes:
> @@ -773,6 +773,14 @@ int cmd_rev_parse(int argc, const char **argv, const
> char *prefix)
> return 1;
> continue;
> }
> + if (opt_with_value(arg, "--ab
On 30/01/2019 12:29, Jeff Hostetler wrote:
>
>
> On 1/26/2019 4:07 PM, Ramsay Jones wrote:
>>
>> Signed-off-by: Ramsay Jones
>> ---
>>
>> Hi Jeff,
>>
>> If you need to re-roll your 'jh/trace2' branch, could you please
>> squash this into the relevant patches (sorry, I didn't look to
>> see wh
On Mon, Feb 04, 2019 at 10:49:05AM +0100, Johannes Schindelin wrote:
> Hi Gábor,
>
> On Sat, 2 Feb 2019, SZEDER Gábor wrote:
>
> > Before installing the necessary dependencies, our OSX build jobs run
> > 'brew update --quiet'. This is problematic for two reasons:
> >
> > - This '--quiet' flag
On Mon, Feb 04, 2019 at 10:26:29AM -0800, Junio C Hamano wrote:
> SZEDER Gábor writes:
>
> > - This '--quiet' flag apparently broke overnight, resulting in
> > errored builds:
> > ...
> > I belive that this breakage will be noticed and fixed soon-ish, so
> > we could probably just w
Hi Jakub,
On Sat, Feb 2, 2019 at 4:39 AM Jakub Narebski wrote:
> I have noticed a little 'recording' indicator; would recorded session
> (video or audio only) be made available at some point in time? Did
> anyone take minutes, or take notes (for example of the Summit agenda
> created at the star
On 04/02/2019 18:12, Junio C Hamano wrote:
> Ramsay Jones writes:
>
>>> Thanks for a detailed and clear explanation here and in the cover
>>> letter. I agree with the motivation and most of the things I see in
>>> this patch, but one thing that stands out at me is if we still want
>>> to += a
Ævar Arnfjörð Bjarmason writes:
> +The algorithm to pick the the current abbreviation length is
> +considered an implementation detail, and might be changed in the
> +future. Since Git version 2.11, the length has been configured to
> +auto-scale based on the estimated number of objects in the
>
On Mon, Feb 4, 2019 at 1:47 PM Junio C Hamano wrote:
> Eric Sunshine writes:
> > On Sun, Feb 3, 2019 at 4:01 PM Sven van Haastregt wrote:
> >> We cannot always rely on successfully invoking `git rev-parse` in the
> >> submodule directory. Keep the old method using `cut` as a fallback.
> >
> > R
Johannes Schindelin writes:
>> I do not recall we crossed the bridge to allow trailing comma here
>> at the end of enum definition.
>
> In advice.c:
>
> enum color_advice {
> ADVICE_COLOR_RESET = 0,
> ADVICE_COLOR_HINT = 1,
> };
>
> In builtin/pack-objects.
The author.email, author.name, committer.email and committer.name
settings are analogous to the GIT_AUTHOR_* and GIT_COMMITTER_*
environment variables, but for the git config system. This allows them
to be set separately for each repository.
Git supports setting different authorship and committer
*** BLURB HERE ***
This update adds back the reference to the EMAIL environment variable.
William Hubbs (1):
config: allow giving separate author and committer idents
Documentation/config/user.txt | 23 ++---
blame.c | 3 +-
builtin/am.c | 1 +
buil
Eric Sunshine writes:
> On Sun, Feb 3, 2019 at 4:01 PM Sven van Haastregt wrote:
>> Until now, `git submodule summary` was always emitting 7-character
>> SHA-1s that have a higher chance of being ambiguous for larger
>> repositories. Use `git rev-parse --short` instead, which will
>> determine
SZEDER Gábor writes:
> Before installing the necessary dependencies, our OSX build jobs run
> 'brew update --quiet'. This is problematic for two reasons:
>
> - This '--quiet' flag apparently broke overnight, resulting in
> errored builds:
> ...
> I belive that this breakage will be not
Nickolai Belakovski writes:
> On Fri, Feb 1, 2019 at 2:54 PM Junio C Hamano wrote:
>>
>>
>> I had to apply and then use --color-words to see what is going on.
>> Please avoid unnecessary reflowing of the text that makes the patch
>> harder than necessary to read.
>
> I was trying to keep the lin
Nickolai Belakovski writes:
> There's been a little back and forth on it, but my understanding is
> that using the colon separator bypasses the caching mechanism in the
> atoms, so every instance of "worktree:path" in a format string would
> require a lookup.
Would that be a problem, though? Yo
Ramsay Jones writes:
>> Thanks for a detailed and clear explanation here and in the cover
>> letter. I agree with the motivation and most of the things I see in
>> this patch, but one thing that stands out at me is if we still want
>> to += append to SP_EXTRA_FLAGS in target specific way. Befor
Duy Nguyen writes:
>> The disadvantage, of course, would be that other call sites would not
>> benefit from a manual auditing whether the argument has side effects (and
>> thus, whether a macro using the argument multiple times would result in
>> very unexpected multiple side effects).
>
> That's
Nguyễn Thái Ngọc Duy writes:
> The description of git-commit jumps right into the commit content, which
> is important, but it fails to mention how the commit is "added" to the
> repository. Update the first paragraph saying a bit more about branch
> update to fill this gap.
>
> While at there,
Shahzad Lone writes:
> Subject: Re: [PATCH v3 [re-fixed] ] [Enhancement] Improve internals /
> refactoring.
Since all patches are attempts by their authors to improve
something, the above has a very low information density. As all the
changes in this patch are about const-ness, it would probab
The algorithm we use to pick the default abbreviation length as a
function of the approximate number of objects is described in the
commit message for e6c587c733 ("abbrev: auto size the default
abbreviation", 2016-09-30), as well as in and downthread of [1], but
it hasn't been documented.
Let's do
I tried to do a partial clone, but it gave me a "bad pack header". Is
there anything I can do to debug this?
I did "git config uploadpack.allowfilter true" in my repo.
Then I went to a scratch directory and did:
$ git clone --filter=blob:limit=10M ssh://localhost/~/git/my_big_repo
remote: Enumerat
On Mon, Feb 4, 2019 at 11:28 AM Оля Тележная wrote:
>
> пн, 4 февр. 2019 г., 10:16 Christian Couder christian.cou...@gmail.com:
>>
>> The application has been submitted on
>> https://summerofcode.withgoogle.com, but it will not be complete until
>> someone else volunteers as an org admin. I volunt
Hi William,
On Tue, 29 Jan 2019, William Hubbs wrote:
> diff --git a/Documentation/config/user.txt b/Documentation/config/user.txt
> index b5b2ba1199..8b31b5fa31 100644
> --- a/Documentation/config/user.txt
> +++ b/Documentation/config/user.txt
> @@ -1,12 +1,19 @@
> -user.email::
> - Your ema
On Mon, Feb 4, 2019 at 6:44 PM Johannes Schindelin
wrote:
>
> Hi Duy,
>
> On Sat, 2 Feb 2019, Duy Nguyen wrote:
>
> > On Sat, Feb 2, 2019 at 4:21 AM Junio C Hamano wrote:
> > >
> > > Dan McGregor writes:
> > >
> > > > Commit 8dd2e88a92 ("http: support file handles for HTTP_KEEP_ERROR",
> > > > 2
Hi Junio,
On Tue, 29 Jan 2019, Junio C Hamano wrote:
> William Hubbs writes:
>
> > diff --git a/cache.h b/cache.h
> > index 009e8b3b15..375be1f68b 100644
> > --- a/cache.h
> > +++ b/cache.h
> > @@ -1494,10 +1494,19 @@ int date_overflows(timestamp_t date);
> > #define IDENT_STRICT
Hi Duy,
On Sat, 2 Feb 2019, Duy Nguyen wrote:
> On Sat, Feb 2, 2019 at 4:21 AM Junio C Hamano wrote:
> >
> > Dan McGregor writes:
> >
> > > Commit 8dd2e88a92 ("http: support file handles for HTTP_KEEP_ERROR",
> > > 2019-01-10) introduced an implicit assumption that rewind, fileno, and
> > > ffl
On Mon, Feb 4, 2019 at 5:36 PM Ævar Arnfjörð Bjarmason wrote:
>
> The documentation saying that diff-tree didn't support anything except
> literal prefixes hasn't been true since
> d38f28093e ("tree_entry_interesting(): support wildcard matching",
> 2010-12-15), but this documentation was not upda
Hi Hannes,
On Sun, 3 Feb 2019, Johannes Sixt wrote:
> strbuf_vinsertf inserts a formatted string in the middle of an existing
> strbuf value. It makes room in the strbuf by moving existing string to
> the back, then formats the string to insert directly into the hole.
>
> It uses vsnprintf to fo
Hi Hannes,
On Mon, 4 Feb 2019, Johannes Sixt wrote:
> Am 03.02.19 um 17:51 schrieb Johannes Sixt:
> > strbuf_vinsertf inserts a formatted string in the middle of an existing
> > strbuf value.
>
> Quite frankly, this is a really unusual operation, and I'd prefer to get
> rid of it. There is only
The documentation saying that diff-tree didn't support anything except
literal prefixes hasn't been true since
d38f28093e ("tree_entry_interesting(): support wildcard matching",
2010-12-15), but this documentation was not updated at the time.
Since this command uses pathspecs like most other comma
On Mon, Feb 4, 2019 at 7:06 AM brian m. carlson
wrote:
>
> When we write an alternate shallow file in update_shallow, we write it
> into the lock file. The string stored in alternate_shallow_file is
> copied from the lock file path, but it is freed the moment that the lock
> file is closed, since
Hi Gábor,
On Sat, 2 Feb 2019, SZEDER Gábor wrote:
> Before installing the necessary dependencies, our OSX build jobs run
> 'brew update --quiet'. This is problematic for two reasons:
>
> - This '--quiet' flag apparently broke overnight, resulting in
> errored builds:
>
> +brew upda
Hi everyone,
There are now ideas, micro-projects and organization application pages
for GSoC 2019 on https://git.github.io/
It would be nice to have a few more project ideas.
https://git.github.io/SoC-2019-Ideas/ currently lists only 2 possible
projects:
- Unify ref-filter formats with other --p
62 matches
Mail list logo
