RE: [RFC] git clone add option to track all remote branches

On April 1, 2018 11:22 PM Junio C Hamano wrote: > Junio C Hamano writes: > > If you are really doing your own development, then you would have some > > topic branches of your own, with forks of some (but most likely not > > all, especiallyi when there are many branches at the

[PATCH 2/2] ls-remote: create option to sort by versions

Updating tests and documentation Signed-off-by: Harald Nordgren --- Documentation/git-ls-remote.txt | 5 + t/t5512-ls-remote.sh| 19 ++- 2 files changed, 23 insertions(+), 1 deletion(-) diff --git a/Documentation/git-ls-remote.txt

Re: [RFC] git clone add option to track all remote branches

Junio C Hamano writes: > If you are really doing your own development, then you would have > some topic branches of your own, with forks of some (but most likely > not all, especiallyi when there are many branches at the upstream) > branches you got from the upstream, and "git

Re: [RFC] git clone add option to track all remote branches

Yubin Ruan writes: > I am writing to ask that whether or not you think will be appropriate to add > an option to "git clone" so that whenever a repo is cloned, branches are > created automatically to track corresponding remote branches. (or is there any > equivelant

[RFC] git clone add option to track all remote branches

Hi, I am writing to ask that whether or not you think will be appropriate to add an option to "git clone" so that whenever a repo is cloned, branches are created automatically to track corresponding remote branches. (or is there any equivelant option?) You can obviously do this by a bash command

Re: [PATCH] Support long format for log-based submodule diff

On Tue, Mar 27, 2018 at 5:17 PM, Stefan Beller wrote: >> >> $ git diff --submodule=log --submodule-log-detail=(long|short) >> >> >> >> I'm not sure what makes sense here. I welcome thoughts/discussion and >> >> will provide follow-up patches. >> > >> > The case of merges is

[PATCH] ls-remote: create option to sort by versions

Create the options '-V ' and '--version-sort' to sort 'git ls-remote' output by version semantics. This is useful e.g. for the Go repository after the release of version 1.10, where otherwise v1.10 is sorted before v1.2. See: $ git ls-remote -t https://go.googlesource.com/go ...

Need help debugging issue in git

I'm struggling with a bug that I found introduced in git v2.13.2. The bug was not reproducible in v2.13.1. The issue is that using arguments like "@{-1}" to aliases causes those curly braces to be removed, so once the command is executed after alias processing the argument looks like "@-1". This

Re: [PATCH] builtin/commit.c: prevent bad commits

On Sun, Apr 01, 2018 at 05:06:50PM +0300, Dan Aloni wrote: > These commits which have hashes starting with the hex string 'bad', > always give me the chills. Why should a perfectly good commit be > jinxed? > > Statistically, one of 4096 commits may be 'bad'. This change adds a > '--prevent-bad'

[PATCH] graph.c: log.showRootMark to indicate root commits

When log.showRootMark is set, root commits are marked with the at sign (@). When log.showRootMark is not set, root commits are marked with the asterisk sign (*). This is the default behavior. Signed-off-by: Lyubomyr Shaydariv --- Documentation/config.txt | 5 +

[ANNOUNCE] Git developers contacted by an advanced alien species

Members of an Alien species that have a far superior technology have recently privately contacted some Git developers. They said that they are amazed by Git technology and mostly wanted to thank us all for our hard work on Git, as they are surely going to use it due to its free software nature.

Proposal

Hello Greetings to you today i asked before but i did't get a response please i know this might come to you as a surprise because you do not know me personally so i will give you a video call to explain more but did you get my previous email ? Let me know asap. Best Regards,

Re: [PATCH] builtin/commit.c: prevent bad commits

Dan Aloni writes: > These commits which have hashes starting with the hex string 'bad', > always give me the chills. Why should a perfectly good commit be > jinxed? > ... > Note that this change does not affect actual software quality maintained > using Git. Thus, it is

Greetings,

Hello Greetings to you today i asked before but i did't get a response please i know this might come to you as a surprise because you do not know me personally so i will give you a video call to explain more but did you get my previous email ? Let me know asap. Best Regards, miss

Re: [GSoC] [PATCH] travis-ci: added clang static analysis

> On 13 Mar 2018, at 18:45, Siddhartha Mishra wrote: > > On Mon, Mar 12, 2018 at 3:49 PM, Lars Schneider > wrote: >> Hi, >> >> That looks interesting but I agree with Dscho that we should not limit >> this to master/maint. >> >> I assume you did

Re: [PATCH v12 04/10] utf8: teach same_encoding() alternative UTF encoding names

> On 16 Mar 2018, at 19:19, Eric Sunshine wrote: > > On Fri, Mar 16, 2018 at 1:50 PM, Junio C Hamano wrote: >> Eric Sunshine writes: >>> However, I'm having a tough time imagining cases in which callers >>> would want

[PATCH] builtin/commit.c: prevent bad commits

These commits which have hashes starting with the hex string 'bad', always give me the chills. Why should a perfectly good commit be jinxed? Statistically, one of 4096 commits may be 'bad'. This change adds a '--prevent-bad' switch to the commit command in order to prevent such commit hashes from

Re: [PATCH v11 06/10] convert: add 'working-tree-encoding' attribute

> On 18 Mar 2018, at 08:24, Torsten Bögershausen wrote: > > Some comments inline > > On Fri, Mar 09, 2018 at 06:35:32PM +0100, lars.schnei...@autodesk.com wrote: >> From: Lars Schneider >> >> Git recognizes files encoded with ASCII or one of its

Re: What's cooking in git.git (Mar 2018, #05; Wed, 28)

> On 30 Mar 2018, at 12:32, Lars Schneider wrote: > > >> On 30 Mar 2018, at 11:24, Ævar Arnfjörð Bjarmason wrote: >> >> >> On Wed, Mar 28 2018, Junio C. Hamano wrote: >> >>> * ls/checkout-encoding (2018-03-16) 10 commits >>> - convert: add round

[PATCH v6 6.5/6] fixup! worktree: teach "add" to check out existing branches

Signed-off-by: Thomas Gummerer --- So while playing with it a bit more I found one case where the new UI is not ideal and a bit confusing. Namely when the new check out dwim kicks in, but there is already a file/directory at the path we're giving to 'git worktree add'. In

URGENT

Re: PRIVATE Dear Madam/Sir, I trust this email finds you in good health. I write in respect of an amount held in the account of an expatriate investor, an associate physician, working on Cancer Vaccines Immunotherapy Research. The closing balance is the sum of US$13, 400, 000 (Thirteen Million and

[GIT PULL] l10n updates for 2.17.0 round 1

Hi Junio, Would you please pull the following git l10n updates. The following changes since commit 0afbf6caa5b16dcfa3074982e5b48e27d452dbbb: Git 2.17-rc0 (2018-03-15 15:01:05 -0700) are available in the Git repository at: git://github.com/git-l10n/git-po tags/l10n-2.17.0-rnd1 for you to