[PATCH 4/6] WIP: mess only with mark_reachable

This still messes up gc/prune on an empty repo where the worktree code can't parse HEAD properly. Bummer. That code sucks for the non-worktree case. Signed-off-by: Michael J Gruber --- reachable.c | 2 +- refs.h | 1 + refs/files-backend.c |

[PATCH 6/6] revisions: list all worktree HEADs with --all

Signed-off-by: Michael J Gruber --- Notes: Note that ever since f0298cf (revision walker: include a detached HEAD in --all, 2009-01-16) the documentation failed to mention the inclusion of HEAD with "--all". Documentation/rev-list-options.txt | 2 +-

Re: What's cooking in git.git (Feb 2016, #07; Thu, 25)

> * jk/tighten-alloc (2016-02-22) 22 commits > (merged to 'next' on 2016-02-24 at 78b3251) > + ewah: convert to REALLOC_ARRAY, etc > + convert ewah/bitmap code to use xmalloc > + diff_populate_gitlink: use a strbuf > + transport_anonymize_url: use xstrfmt > + git-compat-util: drop mempcpy

Re: Rebase performance

Hi Matthieu, On Thu, 25 Feb 2016, Matthieu Moy wrote: > Ævar Arnfjörð Bjarmason writes: > > > At the risk of derailing this thread, a thing that would make rebase > > even faster I think would be to change it so that instead of applying > > a patch at a time to the working

Re: git mv messed up file mapping if folders contain identical files

Hi, On Fri, Feb 26, 2016 at 4:50 AM, SZEDER Gábor wrote: > > Please don't top-post on this list. > Sorry about that. Just learned what that means and why it is bad... > Subject: [PATCH] diffcore: fix iteration order of identical files during > rename detection > > If the two

Restore Question

I have git running on a VMware virtual machine. I backup the virtual machine every day. How do I restore git from a restore of the virtual machine? -- 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

Greetings!

Greetings! Please accept my apology if my mood of contacting you will in any way offend you I wish to seek your assistance for the transfer of fund depository made by a foreign investor for an investment programmed that has remained dormant for years now. I discovered that the account holder

Re: [GSoC] Microproject :- Teaching git pull --rebase the --no-autostash flag

Hi, Some minor nits in addition to Paul's comments: > Subject: Re: [GSoC] Microproject :- Teaching git pull --rebase the > --no-autostash flag The ":-" is typically Indian. Just use ":" here (without a space before). Mehul Jain writes: > With this patch, git pull

Re: [PATCH] Add --no-autostash flag to git pull --rebase

On Fri, Feb 26, 2016 at 7:23 PM, Mehul Jain wrote: > Subject: [PATCH] Add --no-autostash flag to git pull --rebase We usually don't capitalize the first word of the commit title. We also usually prefix the commit title with the relevant subsystem, file or command. So

Re: interactive rebase results across shared histories

On 24 February 2016 at 10:05, Seb wrote: > On Tue, 23 Feb 2016 23:57:06 +0100, > Moritz Neeb wrote: > > [...] > >>> OK, I've followed this advice and looked at the dependency graphs in >>> gitk before and after rebasing, I've managed to obtain what I was

Re: cover letter and cc list

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday 23 March 2015 01:48 PM, Olaf Hering wrote: > On Fri, Mar 20, Junio C Hamano wrote: > >>> Olaf Hering writes: >>> > What does it take to send the cover letter to all people which are > listed in the Cc: list of

Re: [GSoC] Microproject :- Teaching git pull --rebase the --no-autostash flag

On Fri, Feb 26, 2016 at 5:21 PM, Paul Tan wrote: > That was the point of the microproject ;-). --[no-]autostash means > both --autostash and --no-autostash. Oops, my bad. I will add the necessary changes :-). Thanks, Mehul -- To unsubscribe from this list: send the line

Re: git mv messed up file mapping if folders contain identical files

Hi, Please don't top-post on this list. > I guess a bigger concern of this issue is the mess up of history. That > is, even if not doing an merge/update, just doing the 'git mv' will > messed up the file history, as shown in following: > > > // Add a new resources/qa/content.txt files with a

Re: [GSoC] Microproject :- Teaching git pull --rebase the --no-autostash flag

On Fri, Feb 26, 2016 at 7:23 PM, Mehul Jain wrote: > With this patch, git pull --rebase will understand --no-autostash command > line flag. > This flag will override "rebase.autostash" configuration(if set) and leads to > a > failure if current working directory is

[PATCH] Add --no-autostash flag to git pull --rebase

git pull --rebase now understand --no-autostash flag. If directory is found to be dirty then command will die. This flag override "rebase.autostash" configuration(if set). If this flag is not passed in command line then default behaviour is choosen, given by "rebase.autostash"(if

[GSoC] Microproject :- Teaching git pull --rebase the --no-autostash flag

With this patch, git pull --rebase will understand --no-autostash command line flag. This flag will override "rebase.autostash" configuration(if set) and leads to a failure if current working directory is dirty. If "rebase.autostash" is not configured and no flag is passed then by default

Re: [PATCH] upload-pack: use argv_array for pack_objects

On Thu, Feb 25, 2016 at 09:14:01PM -0500, Eric Sunshine wrote: > On Thu, Feb 25, 2016 at 7:13 AM, Michael Procter > wrote: > > Use the argv_array in the child_process structure, to avoid having to > > manually maintain an array size. > > > > Signed-off-by: Michael

[PATCH] credential: let empty credential specs reset helper list

Sine the credential.helper key is a multi-valued config list, there's no way to "unset" a helper once it's been set. So if your system /etc/gitconfig sets one, you can never avoid running it, but only add your own helpers on top. Since an empty value for credential.helper is nonsensical (it would

Re: [PATCH v2 0/2] Remove "push.default unset" warning

On Thu, Feb 25, 2016 at 10:21:58AM +0100, Matthieu Moy wrote: > Junio and Peff both lean towards removing the message completely, and > I think I'm convinced. We would have to do this in the future anyway. Unsurprisingly, this series looks good to me. :) -Peff -- To unsubscribe from this list:

花溪彝族苗族乡

你的老朋友邀你来Q群:343257759

[Q] Import SVN tags into a local Git repository?

[ Please CC me as I am not subscribed to this ML ] Hi, I have here the problem that I build LLVM/Clang out of the official LLVM Git repositories. But version-tagging is done in the LLVM SVN repositories (see announce in [0] "[3.8 Release] RC3 has been tagged"). The according Git repositories

Re: Fwd: git clone does not respect command line options

On Fri, Feb 26, 2016 at 03:23:58PM +0530, Guilherme wrote: > I did try -c credential.helper= and there was a second problem with that > because an unset credential.helper is not the same as an empty > credential.helper. An empty one printed an error because it tried to invoke > 'git-credential-'.

Re: [PATCH] Update diff-highlight

On 22 February 2016 at 04:49, Eric Sunshine wrote: > On Sun, Feb 21, 2016 at 11:14 PM, Peter Dave Hello > wrote: >> From: Peter Dave Hello > > This "From:" line looks suspiciously incorrect. If anything,

Re: [PATCH v2] add DEVELOPER makefile knob to check for acknowledged warnings

On Fri, Feb 26, 2016 at 4:30 PM, Lars Schneider wrote: > >> On 26 Feb 2016, at 10:26, Duy Nguyen wrote: >> >> On Thu, Feb 25, 2016 at 3:42 PM, wrote: >>> +ifdef DEVELOPER >>> + CFLAGS += -Werror \ >>> +

Re: [PATCH v2] add DEVELOPER makefile knob to check for acknowledged warnings

> On 26 Feb 2016, at 10:26, Duy Nguyen wrote: > > On Thu, Feb 25, 2016 at 3:42 PM, wrote: >> +ifdef DEVELOPER >> + CFLAGS += -Werror \ >> + -Wdeclaration-after-statement \ >> +

Re: [PATCH v2] add DEVELOPER makefile knob to check for acknowledged warnings

Thanks for the reviews and the fix :-) Any thought on the "-Wold-style-declaration" problem mentioned in my first v2 email? - Lars > On 25 Feb 2016, at 18:40, Junio C Hamano wrote: > > Perhaps squash these two while queuing to address comments from you two? > > Thanks. >

Re: [PATCH v2] add DEVELOPER makefile knob to check for acknowledged warnings

On Thu, Feb 25, 2016 at 3:42 PM, wrote: > +ifdef DEVELOPER > + CFLAGS += -Werror \ > + -Wdeclaration-after-statement \ > + -Wno-format-zero-length \ > +

Re: Fwd: git clone does not respect command line options

On Fri, Feb 26, 2016 at 03:34:53PM +0700, Duy Nguyen wrote: > On Fri, Feb 26, 2016 at 3:24 PM, Jeff King wrote: > > As an alternative, it would be nice to have some config syntax for > > "clear the list". Maybe something like an empty string, which I think > > has no meaning for

[PATCH v2] contrib/subtree: add repo url to commit messages

For recalling where a subtree came from; git-subtree operations 'add' and 'pull', when called with the parameter add this to the commit message: git-subtree-repo: Other operations that don't have the information, like 'merge' and 'add' without , are unchanged. Users with such a workflow

Re: [PATCH] SubmittingPatches : WIP tag in patches

On 26.02.2016 15:19, Pranit Bauva wrote: > I have to inoculate the habit of signing off every time. There is this in git-config(1); hope that helps. format.signOff A boolean value which lets you enable the -s/--signoff option of format-patch by default. Note: Adding the Signed-off-by:

Re: Fwd: git clone does not respect command line options

On Fri, Feb 26, 2016 at 3:24 PM, Jeff King wrote: > As an alternative, it would be nice to have some config syntax for > "clear the list". Maybe something like an empty string, which I think > has no meaning for the current multi-valued variables (at least not for > credential

Re: [PATCH] contrib/subtree: add repo url to commit messages

On 2016-02-25 17:23-0500, Eric Sunshine wrote: On Tue, Feb 23, 2016 at 5:25 AM, Mathias Nyman wrote: For recalling where a subtree came from; git-subtree operations 'add' and 'pull', when called with the parameter add this to the commit message: git-subtree-repo:

Re: Fwd: git clone does not respect command line options

On Fri, Feb 26, 2016 at 12:15:46AM -0800, Jacob Keller wrote: > On Thu, Feb 25, 2016 at 11:59 PM, Jeff King wrote: > > Right. The "git-config" program doesn't know about the semantics of > > particular values (remember that in the early days, there were many > > porcelains which

Re: [PATCH] SubmittingPatches : WIP tag in patches

On Fri, Feb 26, 2016 at 9:19 AM, Pranit Bauva wrote: > Eric Sunshine: >> On Fri, Feb 26, 2016 at 9:05 AM, Pranit Bauva wrote: >>> --- >> Missing sign-off. > > I have to inoculate the habit of signing off every time. >>> diff --git

Re: Fwd: git clone does not respect command line options

On Thu, Feb 25, 2016 at 11:59 PM, Jeff King wrote: > Right. The "git-config" program doesn't know about the semantics of > particular values (remember that in the early days, there were many > porcelains which built on top of git, and they could all store their own > config). Using

Re: [PATCH] SubmittingPatches : WIP tag in patches

Eric Sunshine: > On Fri, Feb 26, 2016 at 9:05 AM, Pranit Bauva wrote: >> --- > > Missing sign-off. > I have to inoculate the habit of signing off every time. >> diff --git a/Documentation/SubmittingPatches >> @@ -168,7 +168,9 @@ the closing bracket to mark the nature of

Re: [PATCH 01/16] bisect: write about `bisect next` in documentation

On Thu, Feb 25, 2016 at 6:04 PM, Stephan Beyer wrote: > This patch considers the source code comment that says to be > "not sure we want 'next' at the UI level anymore", and replies with > "Yes, we want it!". Therefore, the "git bisect next" functionality > is explicitly

Re: [PATCH] SubmittingPatches : WIP tag in patches

On Fri, Feb 26, 2016 at 9:05 AM, Pranit Bauva wrote: > --- Missing sign-off. > diff --git a/Documentation/SubmittingPatches > @@ -168,7 +168,9 @@ the closing bracket to mark the nature of the patch > is also > encouraged. E.g. [PATCH/RFC] is often used when the patch is

Re: Fwd: git clone does not respect command line options

On Fri, Feb 26, 2016 at 01:16:39PM +0530, Guilherme wrote: > Is there any documentation on which variables are muli-valued? There's no central registry. It's often mentioned in the documentation for a particular config option, but it looks like the credential.* config is not very clear about

<    1   2