In a private repository, I have set of tags which are mostly linear
(each tag contains the previous one). I have created this repo with
fast-export --anonomize to reproduce the issue and it is available at
https://github.com/tarm/git_describe_repo.
Recently I ran git describe, but I did not get th
On Mon, 2015-12-21 at 15:34 -0800, Junio C Hamano wrote:
> Great. Thanks, will queue w/o 1/2 (though I do not think it would
> hurt).
>
> On Mon, Dec 21, 2015 at 3:33 PM, David Turner <
> dtur...@twopensource.com> wrote:
> > On Mon, 2015-12-21 at 15:27 -0800, Junio C Hamano wrote:
> > > Thanks. D
On Mon, Dec 21, 2015 at 9:09 PM, Stephen P. Smith wrote:
> Add a section to the users manual documenting shallow clones.
For the subject, prefix by section/module you're touching; drop
capitalization; drop full-stop (period).
> The todo section previously noted that documentation of shallow clon
On Mon, Dec 21, 2015 at 9:09 PM, Stephen P. Smith wrote:
> There are several places in the documentation that
> the term shallow clone is used. Defining the term
> enables its use elsewhere with a known definition.
>
> Signed-off-by: Stephen P. Smith
> ---
> diff --git a/Documentation/glossary-co
There are several places in the documentation that
the term shallow clone is used. Defining the term
enables its use elsewhere with a known definition.
Signed-off-by: Stephen P. Smith
---
Documentation/glossary-content.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/glo
The todo section previously noted that documentation of shallow clones
was not in the manual and had references to the 1.5.0 release notes.
The patch adds a section to the manual and removes the entry in the
ToDo list.
Signed-off-by: Stephen P. Smith
---
Notes:
I considered adding a paragra
On Tue, Dec 22, 2015 at 1:31 AM, Junio C Hamano wrote:
> Junio C Hamano writes:
>
>> Nguyễn Thái Ngọc Duy writes:
>>
>>> This commit has caused three regression reports so far. All of them are
>>> about spawning git subprocesses, where the new presence of GIT_WORK_TREE
>>> either changes comman
On Mon, Dec 21, 2015 at 12:50:28PM -0800, Junio C Hamano wrote:
> Jeff King writes:
>
> > #ifndef NO_SYMLINK_HEAD
> > - if (prefer_symlink_refs) {
> > - unlink(ref_path);
> > - if (!symlink(target, ref_path))
> > - goto done;
>
> I see that the original
On Mon, 2015-12-21 at 15:27 -0800, Junio C Hamano wrote:
> Thanks. Does the number still stay at 25% improvement?
Yes.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-i
Thanks. Does the number still stay at 25% improvement?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, 2015-12-21 at 17:34 -0500, David Turner wrote:
> We don't usually modify traverse_info, so make it const across a wide
> range of functions.
>
> Signed-off-by: David Turner
> ---
> builtin/merge-tree.c | 2 +-
> cache-tree.c | 4 ++--
> cache-tree.h | 2 +-
We don't usually modify traverse_info, so make it const across a wide
range of functions.
Signed-off-by: David Turner
---
builtin/merge-tree.c | 2 +-
cache-tree.c | 4 ++--
cache-tree.h | 2 +-
t/t4010-diff-pathspec.sh | 2 +-
tree-walk.c | 2 +-
tr
In traverse_trees, we generate the complete traverse path for a
traverse_info. Later, in do_compare_entry, we used to go do a bunch
of work to compare the traverse_info to a cache_entry's name without
computing that path. But since we already have that path, we don't
need to do all that work. In
This version strdups the path to avoid it getting mutated. Problem
noted by Junio.
David Turner (2):
traverse_info: make mostly const
do_compare_entry: use already-computed path
builtin/merge-tree.c | 2 +-
cache-tree.c | 4 ++--
cache-tree.h | 2 +-
t/t4010-
Thanks. I wiggled these three on top of the "Revert the earlier
one"; while I think the result is correct, I'd appreciate if you can
double check the result when I push the topic out later today.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord.
Alan Mackenzie wrote: on Mon, 21 Dec 2015 14:29:54
> Hello, git project.
> Last night, whilst clearing out a stale "stash stack", I did "git stash
> pop". There were conflicts in two files.
> However, all the popped files became staged. This doesn't normally happen.
> It was intensely irritati
Jeff King writes:
> #ifndef NO_SYMLINK_HEAD
> - if (prefer_symlink_refs) {
> - unlink(ref_path);
> - if (!symlink(target, ref_path))
> - goto done;
I see that the original was sloppy (most certainly my bad) ...
> + char *ref_path = get_locked
larsxschnei...@gmail.com writes:
> From: Lars Schneider
>
> If tests are executed in verbose mode then the retry logic clutters the
> test output. Suppress that clutter.
>
> Signed-off-by: Lars Schneider
> ---
> t/lib-git-p4.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --
larsxschnei...@gmail.com writes:
> From: Lars Schneider
>
> Hi,
>
> these patches extend "git-p4: add trap to kill p4d on test exit" (dfe90e8)
> and therefore should be applied on master.
Wait, wait. Please be a bit more careful when you use such a
phrasing. Did somebody review these and said
From: "Torsten Bögershausen"
On 2015-12-21 18.37, Junio C Hamano wrote:
Duy Nguyen writes:
On Mon, Dec 21, 2015 at 6:01 PM, Philip Oakley
wrote:
On the Git User's list, Diego J. reported that:
'When I "checkout" a branch using different Upper Case/Lower Case than
the
original, the bran
On Mon, Dec 21, 2015 at 2:55 PM, Stephen & Linda Smith wrote:
> On Sunday, December 20, 2015 06:27:56 PM Stephen & Linda Smith wrote:
>> I've been looking over the git source tree to see if there is some place
>> where I can
>> contribute. It appears that there are some suggestions at the botto
On Sunday, December 20, 2015 06:27:56 PM Stephen & Linda Smith wrote:
> I've been looking over the git source tree to see if there is some place
> where I can
> contribute. It appears that there are some suggestions at the bottom of
> the userguide. Does anyone have other places that they wou
On Monday, December 21, 2015, Julian Andres Klode wrote:
> Introduce an option to deny unsigned tags from entering
> a repository. This is useful in teams where members forget
> to sign their release tags.
>
> It does not actually check whether the signature is actually
> complete or valid, it jus
Thanks, will replace what was queued on 'pu'.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Junio C Hamano writes:
> Use of "cat-file -p" is a bad manner in scripts, as we reserve the
> right to change what "-p" output looks like purely on human
> usability. "cat-file tag", perhaps?
>
> Also,
>
> $ git grep ' PGP '
>
> in our source tells me that we use a bit tighter pattern even
Junio C Hamano writes:
> Nguyễn Thái Ngọc Duy writes:
>
>> This commit has caused three regression reports so far. All of them are
>> about spawning git subprocesses, where the new presence of GIT_WORK_TREE
>> either changes command behaviour (git-init or git-clone), or how
>> repo/worktree is
Duy Nguyen writes:
> On Thu, Dec 17, 2015 at 2:44 PM, Jeff King wrote:
>> I think we may actually be thinking of the same thing. Naively, I would
>> expect:
>>
>> ..
>> - if there is cache data in the index but that config flag is not set,
>> presumably we would not update it (we could eve
On 2015-12-21 18.37, Junio C Hamano wrote:
> Duy Nguyen writes:
>
>> On Mon, Dec 21, 2015 at 6:01 PM, Philip Oakley wrote:
>>> On the Git User's list, Diego J. reported that:
>>>
>>> 'When I "checkout" a branch using different Upper Case/Lower Case than the
>>> original, the branch doesn't show
Julian Andres Klode writes:
> Introduce an option to deny unsigned tags from entering
> a repository. This is useful in teams where members forget
> to sign their release tags.
>
> It does not actually check whether the signature is actually
> complete or valid, it just checks for the beginning o
Duy Nguyen writes:
> On Mon, Dec 21, 2015 at 6:01 PM, Philip Oakley wrote:
>> On the Git User's list, Diego J. reported that:
>>
>> 'When I "checkout" a branch using different Upper Case/Lower Case than the
>> original, the branch doesn't show in "git branch [--list]"' [1]
>>
>> While case sensi
Introduce an option to deny unsigned tags from entering
a repository. This is useful in teams where members forget
to sign their release tags.
It does not actually check whether the signature is actually
complete or valid, it just checks for the beginning of a
signature, as further checks would be
Nguyễn Thái Ngọc Duy writes:
> This commit has caused three regression reports so far. All of them are
> about spawning git subprocesses, where the new presence of GIT_WORK_TREE
> either changes command behaviour (git-init or git-clone), or how
> repo/worktree is detected (from aliases), with or
Jeff King writes:
> On Sun, Dec 20, 2015 at 05:31:48PM -0800, Junio C Hamano wrote:
>
>> Actually, we do not even _need_ a sharedness for this ephemeral
>> file. The additional "adjust-shared-perm" is merely a workaround
>> for the fact the next person cannot write into it when it is left
>> beh
Hi everyone,
when I get an email with a patch attached, instead of inline, and save
the attachment; the first line "From ..." has a ">" in front of
it, which causes git-am to not recognize the patch format.
Would it be possible to just ignore the > on that line and then read
the patch correctly?
David Turner writes:
> In traverse_trees, we generate the complete traverse path for a
> traverse_info. Later, in do_compare_entry, we used to go do a bunch
> of work to compare the traverse_info to a cache_entry's name without
> computing that path. But since we already have that path, we don'
Johannes Sixt writes:
>> +#undef write
>> +ssize_t mingw_write(int fd, const void *buf, size_t len)
>> +{
>> +ssize_t result = write(fd, buf, len);
>> +
>> +if (result < 0 && errno == EINVAL && buf) {
>> +/* check if fd is a pipe */
>> +HANDLE h = (HANDLE) _get_osf
Paul Mackerras writes:
> On Tue, Dec 15, 2015 at 03:09:44PM -0800, Junio C Hamano wrote:
>> Git 2.7-rc1 has just been tagged, and the remainder of the year will
>> be for the stabilization, fixes to brown-paper-bag bugs, reverts of
>> regressions, etc., but I haven't seen updates to the various
>
SZEDER Gábor writes:
>> On the other hand, I've marked a handful of topics below as "Will
>> discard". They were all dormant after waiting for updates for quite
>> a long time; interested people may want to help resurrect them.
>
>> * sg/pretty-more-date-mode-format (2015-10-07) 1 commit
>> - pr
On 2015-12-16 19.04, Junio C Hamano wrote:
> Thanks. In the meantime, I'll pick up v6 $gmane/282061 and replace
> the above with it.
I'm looking for a replacement for the grep/sed combination, but no luck with
different trial.
Can anybody help me out, please ?
git ls-files --eol -o | grep "TeBi_"
Hello, git project.
Last night, whilst clearing out a stale "stash stack", I did "git stash
pop". There were conflicts in two files.
However, all the popped files became staged. This doesn't normally happen.
It was intensely irritating, and required me to do "git reset HEAD" on
each of the file
After changing the type of a file in the git repository, it is not possible to
"git p4 publish" the commit to perforce. This is due to the fact that the git
"T" status is not handled in git-p4.py. This can typically occur when replacing
an existing file with a symbolic link.
The "T" modifier is no
On Mon, Dec 21, 2015 at 6:01 PM, Philip Oakley wrote:
> On the Git User's list, Diego J. reported that:
>
> 'When I "checkout" a branch using different Upper Case/Lower Case than the
> original, the branch doesn't show in "git branch [--list]"' [1]
>
> While case sensitivity for filenames is a com
On the Git User's list, Diego J. reported that:
'When I "checkout" a branch using different Upper Case/Lower Case than the
original, the branch doesn't show in "git branch [--list]"' [1]
While case sensitivity for filenames is a common issue on Windows and the
like, I haven't seen any discussion
This commit has caused three regression reports so far. All of them are
about spawning git subprocesses, where the new presence of GIT_WORK_TREE
either changes command behaviour (git-init or git-clone), or how
repo/worktree is detected (from aliases), with or without $GIT_DIR.
The original bug will
On Mon, Dec 21, 2015 at 8:17 AM, Duy Nguyen wrote:
> On Fri, Dec 18, 2015 at 8:35 AM, Cameron Esfahani wrote:
>> I have git project checked out at ~/llvm. Inside of there, inside of a
>> “tools” directory, I have another project checked out as “lldb”:
>>
>> ~/llvm/tools/lldb
>>
>> I wrote an al
45 matches
Mail list logo
