Re: What exactly is a "initial checkout"

On 07/11/2018 08:50, Christian Halstrick wrote: Ok, I know understand the problems which are solved by this special behaviour of a "initial checkout". And also important I understand when exactly I should do a "initial checkout" - when the index file does not exist. I'll share my new knowledge

Re: if YOU use a Windows GUI for Git, i would appreciate knowing which one and why

Hi Gerry, I'll give my view, as someone approaching retirement, but who worked as an Engineer in a mainly Windows environment. On 04/11/2018 17:48, _g e r r y _ _l o w r y _ wrote: PREAMBLE [START] - please feel free to skip this first section Forgive me for asking this question on a mailing

Re: Git Slowness on Windows w/o Internet

On 03/11/2018 16:44, brian m. carlson wrote: On Fri, Nov 02, 2018 at 11:10:51AM -0500, Peter Kostyukov wrote: Wanted to bring to your attention an issue that we discovered on our Windows Jenkins nodes with git scm installed (git.exe). Our Jenkins servers don't have Internet access. It appears

Re: git projects with submodules in different sites - in txt format (:+(

On 02/10/2018 06:47, Michele Hallak wrote: Hi, I am getting out of idea about how to change the methodology we are using in order to ease our integration process... Close to despair, I am throwing the question to you... We have 6 infrastructure repositories [A, B, C, D, E, F ?]. Each

[PATCH 0/1] Re: git silently ignores include directive with single quotes

comment on whether these changes would have assisted in debugging the faulty config file. Philip Oakley (1): config doc: highlight the name=value syntax Documentation/config.txt | 16 1 file changed, 12 insertions(+), 4 deletions(-) -- 2.17.1.windows.2

[PATCH 1/1] config doc: highlight the name=value syntax

regarding pathnames. In addition clarify that missing include file paths are not an error, but rather an implicit 'if found' for include files. [1] https://public-inbox.org/git/ca2b192e-1722-092e-2c54-d79d21a66...@stason.org/ Reported-by: Stas Bekman Signed-off-by: Philip Oakley

Re: Receiving console output from GIT 10mins after abort/termination?

From: "Frank Wolf" Sent: Wednesday, July 18, 2018 7:38 AM Hi @ll, I hope I'm posting to the right group (not sure if it's Windows related) but I've got a weird problem using GIT: By accident I've tried to push a repository (containing an already commited but not yet pushed submodule

Re: git-gui ignores core.hooksPath

From: "Johannes Schindelin" Hi Phillip, On Wed, 14 Jun 2017, Philipp Gortan wrote: thanks for following up, > Indeed. Why don't you give it a try? Actually, I already did: https://github.com/patthoyts/git-gui/pull/12 You might want to post your analysis and patch there as well... I

Re: [RFC PATCH 4/6] sequencer.c: avoid empty statements at top level

From: "Eric Sunshine" To: "Beat Bolli" On Sun, Jul 8, 2018 at 10:44 AM Beat Bolli wrote: The marco GIT_PATH_FUNC expands to a complete statement including the s/marco/macro/ semicolon. Remove two extra trailing semicolons. Signed-off-by: Beat Bolli --- sequencer.c | 4 ++-- 1 file

Re: [msysGit] Possible git status problem at case insensitive file system

Hi Frank, Your system Clock looks to be providing the wrong date for your emails. The last XP version was https://github.com/git-for-windows/git/releases/tag/v2.10.0.windows.1 so you may want to upgrade to that. (see FAQs https://github.com/git-for-windows/git/wiki/FAQ) It won't solve the

Re: GDPR compliance best practices?

From: "Theodore Y. Ts'o" Sent: Friday, June 08, 2018 3:53 AM On Fri, Jun 08, 2018 at 01:21:29AM +0200, Peter Backes wrote: On Thu, Jun 07, 2018 at 03:38:49PM -0700, David Lang wrote: > > Again: The GDPR certainly allows you to keep a proof of copyright > > privately if you have it. However, it

Re: GDPR compliance best practices?

Hi Peter, David, I thought that the legal notice (aka 'disclaimer') was pretty reaonable. Some of Peter's fine distinctions may be technically valid, but that does not stop there being legal grounds. The proof of copyright is a legal grounds. Unfortunately once one gets into legal

Re: GDPR compliance best practices?

Hi Peter, (lost the cc's) From: "Peter Backes" On Sun, Jun 03, 2018 at 11:28:43PM +0100, Philip Oakley wrote: It is here that Article 6 kicks in as to whether the 'organisation' can retain the data and continue to use it. Article 6 is not about continuing to use data. Article

Re: GDPR compliance best practices?

From: "Peter Backes" On Sun, Jun 03, 2018 at 04:28:31PM +0100, Philip Oakley wrote: In most Git cases that legal/legitimate purpose is the copyright licence, and/or corporate employment. That is, Jane wrote it, hence X has a legal rights of use, and we need to have a record of that (

Re: GDPR compliance best practices?

correcting a negative /with/without/ and inserting a comma. - Original Message - From: "Philip Oakley" [snip] From a personal view, many folk want it to be that corporates (and open source organisations) should hold no personal information with having s/with/without/

Re: git glob pattern in .gitignore and git command

Hi Yubun, From: "Yubin Ruan" To ignore all .js file under a directory `lib', I can use "lib/**/js" to match them. But when using git command such as "git add", using "git add lib/\*.js" is sufficient. Why is this difference in glob mode? I have heard that there are many different glob mode

Re: [PATCH v2] t/perf/run: Use proper "--get-regexp", not "--get-regex"

From: "Robert P. J. Day" On Sun, 3 Jun 2018, Thomas Gummerer wrote: > Subject: [PATCH v2] t/perf/run: Use proper "--get-regexp", not micronit: we prefer starting with a lowercase letter after the "area:" prefix in commit messages. Junio can probably fix that while queuing, so no need to

Re: GDPR compliance best practices?

From: "Peter Backes" On Sun, Jun 03, 2018 at 02:59:26PM +0200, Ævar Arnfjörð Bjarmason wrote: I'm not trying to be selfish, I'm just trying to counter your literal reading of the law with a comment of "it'll depend". Just like there's a law against public urination in many places, but this is

Re: git rebase -i --exec and changing directory

Hi Ondrej, Phillip, From: "Phillip Wood" <phillip.w...@talktalk.net> Hi Ondrej On 27/05/18 13:53, Ondrej Mosnáček wrote: Hi Philip, 2018-05-27 14:28 GMT+02:00 Philip Oakley <philipoak...@iee.org>: You may need to give a bit more background of things that seem obvi

Re: git rebase -i --exec and changing directory

Hi Ondrej, Phillip, From: "Phillip Wood" <phillip.w...@talktalk.net> Hi Ondrej On 27/05/18 13:53, Ondrej Mosnáček wrote: Hi Philip, 2018-05-27 14:28 GMT+02:00 Philip Oakley <philipoak...@iee.org>: You may need to give a bit more background of things that seem obvi

Re: git rebase -i --exec and changing directory

You may need to give a bit more background of things that seem obvious to you. So where is the src directory you are cd'ing to relative to the directory/repository you are creating? What is [the name of] the directory you are currently in, etc. ? Philip -- From: "Ondrej Mosnáček"

Re: Troubles with picking an editor during Git update

Hi Bartosz, From: "Bartosz Konikiewicz" Hi there! I had an issue with Git installer for Windows while trying to update The Git for Windows package is managed, via https://gitforwindows.org/, as a separate application, based on Git. my instance of the software. My

Re: Re: [PATCH 1/3] checkout.c: add strict usage of -- before file_path

From: "Dannier Castro L" On 13/05/2018 00:03, Duy Nguyen wrote: On Sun, May 13, 2018 at 4:23 AM, Dannier Castro L wrote: For GIT new users, this complicated versatility of could be very confused, also considering that actually the flag '--' is

Re: [PATCH v6 11/13] command-list.txt: documentation and guide line

Hi Duy, From: "Nguyễn Thái Ngọc Duy" : Monday, May 07, 2018 This is intended to help anybody who needs to update command-list.txt. It gives a brief introduction of all attributes a command can take. --- command-list.txt | 44 1

Re: [PATCH 11/18] branch-diff: add tests

From: "Johannes Schindelin" From: Thomas Rast These are essentially lifted from https://github.com/trast/tbdiff, with light touch-ups to account for the new command name. Apart from renaming `tbdiff` to `branch-diff`, only one test case needed

Re: [PATCH 0/4] subtree: move out of contrib

From: "Ævar Arnfjörð Bjarmason" I think at this point git-subtree is widely used enough to move out of contrib/, maybe others disagree, but patches are always better for discussion that patch-less ML posts. Assuming this lands in Git, then there will also need to be a

Re: Branch deletion question / possible bug?

From: "Jacob Keller" On Fri, Apr 27, 2018 at 5:29 PM, Tang (US), Pik S wrote: Hi, I discovered that I was able to delete the feature branch I was in, due to some fat fingering on my part and case insensitivity. I never realized this could be

Re: [PATCH v6 11/11] Remove obsolete script to convert grafts to replace refs

From: "Johannes Schindelin" The functionality is now implemented as `git replace --convert-graft-file`. A rather late in the day thought: Should this go through the same deprecation dance? I.e. replace the body of the script with the new `git replace

Re: [PATCH v3 09/11] technical/shallow: describe the relationship with replace refs

Hi dscho From: "Johannes Schindelin" <johannes.schinde...@gmx.de> : Tuesday, April 24, 2018 8:10 PM On Sun, 22 Apr 2018, Philip Oakley wrote: From: "Johannes Schindelin" <johannes.schinde...@gmx.de> > Now that grafts are deprecated, we should start to assu

Re: [PATCH v8 06/16] sequencer: introduce the `merge` command

From: "Johannes Schindelin" <johannes.schinde...@gmx.de> On Mon, 23 Apr 2018, Philip Oakley wrote: From: "Johannes Schindelin" <johannes.schinde...@gmx.de> : Monday, April 23, 2018 1:03 PM Subject: Re: [PATCH v8 06/16] sequencer: introduce the `merge` c

Re: [PATCH v8 06/16] sequencer: introduce the `merge` command

From: "Johannes Schindelin" : Monday, April 23, 2018 1:03 PM Subject: Re: [PATCH v8 06/16] sequencer: introduce the `merge` command Hi Philip, [...] > label onto > > # Branch abc > reset onto Is this reset strictly necessary. We are already there @head.

Re: [PATCH v8 06/16] sequencer: introduce the `merge` command

From: "Johannes Schindelin" This patch is part of the effort to reimplement `--preserve-merges` with a substantially improved design, a design that has been developed in the Git for Windows project to maintain the dozens of Windows-specific patch series on top of

Re: [PATCH 3/3] Avoid multiple PREFIX definitions

From: "Johannes Schindelin" <johannes.schinde...@gmx.de> From: Philip Oakley <philipoak...@iee.org> The short and sweet PREFIX can be confused when used in many places. Rename both usages to better describe their purpose. EXEC_CMD_PREFIX is used in full to disambigu

Re: [PATCH v3 09/11] technical/shallow: describe the relationship with replace refs

From: "Johannes Schindelin" Now that grafts are deprecated, we should start to assume that readers have no idea what grafts are. So it makes more sense to describe the "shallow" feature in terms of replace refs. Suggested-by: Eric Sunshine

Re: [PATCH v8 09/16] rebase: introduce the --rebase-merges option

From: "Johannes Schindelin" Once upon a time, this here developer thought: wouldn't it be nice if, say, Git for Windows' patches on top of core Git could be represented as a thicket of branches, and be rebased on top of core Git in order to maintain a

Re: [PATCH v8 09/16] rebase: introduce the --rebase-merges option

From: "Johannes Schindelin" Once upon a time, this here developer thought: wouldn't it be nice if, say, Git for Windows' patches on top of core Git could be represented as a thicket of branches, and be rebased on top of core Git in order to maintain a

Re: [PATCH v8 08/16] rebase-helper --make-script: introduce a flag to rebase merges

From: "Johannes Schindelin" Sorry for the very late in the series comments.. The sequencer just learned new commands intended to recreate branch structure (similar in spirit to --preserve-merges, but with a substantially less-broken design). Let's allow the

Re: [PATCH v8 06/16] sequencer: introduce the `merge` command

From: "Johannes Schindelin" This patch is part of the effort to reimplement `--preserve-merges` with a substantially improved design, a design that has been developed in the Git for Windows project to maintain the dozens of Windows-specific patch series on top of

Re: [PATCH/RFC 0/5] Keep all info in command-list.txt in git binary

From: "Duy Nguyen" <pclo...@gmail.com> On Wed, Apr 18, 2018 at 12:47 AM, Philip Oakley <philipoak...@iee.org> wrote: > Is that something I should add to my todo to add a 'guide' category > > etc.? I added it too [1]. Not sure if you want anything more o

Re: [PATCH/RFC 0/5] Keep all info in command-list.txt in git binary

From: "Philip Oakley" <philipoak...@iee.org> : Tuesday, April 17, 2018 11:47 PM From: "Duy Nguyen" <pclo...@gmail.com> : Tuesday, April 17, 2018 5:48 PM On Tue, Apr 17, 2018 at 06:24:41PM +0200, Duy Nguyen wrote: On Sun, Apr 15, 2018 at 11:21 PM, Philip Oak

Re: [PATCH/RFC 0/5] Keep all info in command-list.txt in git binary

From: "Duy Nguyen" <pclo...@gmail.com> : Tuesday, April 17, 2018 5:48 PM On Tue, Apr 17, 2018 at 06:24:41PM +0200, Duy Nguyen wrote: On Sun, Apr 15, 2018 at 11:21 PM, Philip Oakley <philipoak...@iee.org> wrote: > From: "Duy Nguyen" <pclo...@gmail.com&

Re: [PATCH/RFC 0/5] Keep all info in command-list.txt in git binary

From: "Duy Nguyen" <pclo...@gmail.com> : Saturday, April 14, 2018 4:44 PM On Thu, Apr 12, 2018 at 12:06 AM, Philip Oakley <philipoak...@iee.org> wrote: I'm only just catching up, but does/can this series also capture the non-command guides that are available in git so that

Re: [PATCH v6 04/15] sequencer: introduce new commands to reset the revision

From: "Phillip Wood" : Friday, April 13, 2018 11:03 AM If a label or reset command fails it is likely to be due to a typo. Rescheduling the command would make it easier for the user to fix the problem as they can just run 'git rebase --edit-todo'. Is this worth

Re: [PATCH/RFC 0/5] Keep all info in command-list.txt in git binary

From: "Eric Sunshine" Monday, April 09, 2018 6:17 AM On Mon, Mar 26, 2018 at 12:55 PM, Nguyễn Thái Ngọc Duy wrote: This is pretty rough but I'd like to see how people feel about this first. I notice we have two places for command classification.

Re: Bug: duplicate sections in .git/config after remote removal

From: "Ævar Arnfjörð Bjarmason" On Tue, Mar 27 2018, Jason Frey wrote: While the impact of this bug is minimal, and git itself is not affected, it can affect external tools that want to read the .git/config file, expecting unique section names. To reproduce: Given the

Re: Bug: duplicate sections in .git/config after remote removal

From: "Ævar Arnfjörð Bjarmason" On Tue, Mar 27 2018, Jason Frey wrote: While the impact of this bug is minimal, and git itself is not affected, it can affect external tools that want to read the .git/config file, expecting unique section names. To reproduce: Given the

Re: Bug: duplicate sections in .git/config after remote removal

From: "Ævar Arnfjörð Bjarmason" On Tue, Mar 27 2018, Jason Frey wrote: While the impact of this bug is minimal, and git itself is not affected, it can affect external tools that want to read the .git/config file, expecting unique section names. To reproduce: Given the

Re: Bug: duplicate sections in .git/config after remote removal

From: "Ævar Arnfjörð Bjarmason" On Tue, Mar 27 2018, Jason Frey wrote: While the impact of this bug is minimal, and git itself is not affected, it can affect external tools that want to read the .git/config file, expecting unique section names. To reproduce: Given the

Re: [ANNOUNCE] Git Rev News edition 37

From: "Christian Couder" Hi everyone, The 37th edition of Git Rev News is now published: https://git.github.io/rev_news/2018/03/21/edition-37/ Thanks a lot to all the contributors! Enjoy, Christian, Jakub, Markus and Gabriel. Thank you for the Git Rev News.

Re: Crash when clone includes magic filenames on Windows

From: "Philip Oakley" <philipoak...@iee.org> From: "Jeffrey Walton" <noloa...@gmail.com> Hi Everyone, I'm seeing this issue on Windows: https://pastebin.com/YfB25E4T . It seems the filename AUX is the culprit. Also see https://blogs.msdn.microsoft.com/oldnewthin

Re: Crash when clone includes magic filenames on Windows

From: "Jeffrey Walton" Hi Everyone, I'm seeing this issue on Windows: https://pastebin.com/YfB25E4T . It seems the filename AUX is the culprit. Also see https://blogs.msdn.microsoft.com/oldnewthing/20031022-00/?p=42073 . (Thanks to Milleneumbug on Stack Overflow). I did

Re: "git bisect run make" adequate to locate first unbuildable commit?

From: "Robert P. J. Day" <rpj...@crashcourse.ca> On Fri, 9 Feb 2018, Philip Oakley, CEng MIET wrote: (apologies for using the fancy letters after the name ID...) From: "Robert P. J. Day" <rpj...@crashcourse.ca> > > writing a short tutorial on "gi

Re: "git bisect run make" adequate to locate first unbuildable commit?

From: "Robert P. J. Day" writing a short tutorial on "git bisect" and, all the details of special exit code 125 aside, if one wanted to locate the first unbuildable commit, would it be sufficient to just run? $ git bisect run make as i read it, make returns either

RE: git send-email sets date

Behalf Of brian m. carlson > On Fri, Jan 26, 2018 at 06:32:30PM +0100, Michal Suchánek wrote: > > git send-email sets the message date to author date. > > > > This is wrong because the message will most likely not get delivered > > when the author date differs from current time. It might give

Re: [PATCH 3/3] perf/aggregate: sort JSON fields in output

From: "Christian Couder" It is much easier to diff the output against a preivous s/preivous/previous/ one when the fields are sorted. Signed-off-by: Christian Couder --- t/perf/aggregate.perl | 2 +- 1 file changed, 1 insertion(+), 1

Re: cygwin git and golang: how @{u} is handled

From: "John Cheng" I am experiencing a strange behavior and I'm not certain if it is a problem with golang or the cygwin version of git. Steps to reproduce: Use golang's os/exec library to execute exec.Command(os.Args[1],"log","@{u}") // where os.Args[1] is either cygwin

Re: [PATCH 10/8] [DO NOT APPLY, but improve?] rebase--interactive: introduce "stop" command

From: "Jacob Keller" On Thu, Jan 18, 2018 at 10:36 AM, Stefan Beller wrote: Jake suggested using "x false" instead of "edit" for some corner cases. I do prefer using "x false" for all kinds of things such as stopping before a commit (edit only

Re: [PATCH 8/8] rebase -i: introduce --recreate-merges=no-rebase-cousins

From: "Johannes Schindelin" This one is a bit tricky to explain, so let's try with a diagram: C / \ A - B - E - F \ / D To illustrate what this new mode is all about, let's consider what happens upon `git rebase -i --recreate-merges B`, in

Re: [PATCH 4/8] rebase-helper --make-script: introduce a flag to recreate merges

From: "Johannes Schindelin" The sequencer just learned a new commands intended to recreate branch structure (similar in spirit to --preserve-merges, but with a substantially less-broken design). Let's allow the rebase--helper to generate todo lists making use of

Re: [PATCH 1/8] sequencer: introduce new commands to reset the revision

From: "Jacob Keller" On Thu, Jan 18, 2018 at 7:35 AM, Johannes Schindelin wrote: This commit implements the commands to label, and to reset to, given revisions. The syntax is: label reset As a convenience shortcut, also

Re: [PATCH] Remoted unnecessary void* from hashmap.h that caused compile warnings

From: Subject: [PATCH] Remoted unnecessary void* from hashmap.h that caused compile warnings s/Remoted/Removed/ ? Maybe shorten to " hashmap.h: remove unnecessary void* " (ex the superflous spaces) -- Philip From: "Randall S. Becker"

Re: [PATCH/RFC] diff: add --compact-summary option to complement --stat

(one spelling spotted).. From: "Nguyễn Thái Ngọc Duy" This is partly inspired by gerrit web interface which shows diffstat like this, e.g. with commit 0433d533f1 (notice the "A" column on the third line): Documentation/merge-config.txt | 4 + builtin/merge.c

Re: Errors and other unpleasant things found by Cppcheck

From: "Friedrich Spee von Langenfeld" Hi, I analyzed the GitHub repository with Cppcheck. The resulting XML file is attached. Please open it in Cppcheck to view it comfortably. Especially the bunch of errors could be of interest to you. Hi, Thanks for the submission.

Re: Re: Unify annotated and non-annotated tags

From: "anatoly techtonik" <techto...@gmail.com> From: Philip Oakley > So if I understand correctly, the hope is that `git show-ref --tags` > could > get an alternate option `--all-tags` [proper option name required...] > such > that the user would not

Re: [WIP 12/15] ls-refs: introduce ls-refs server command

From: "Brandon Williams" Sent: Monday, December 04, 2017 11:58 PM Introduce the ls-refs server command. In protocol v2, the ls-refs command is used to request the ref advertisement from the server. Since it is a command which can be requested (as opposed to manditory in

Re: [PATCH 0/8] Codespeed perf results

From: "Christian Couder" This patch series is built on top of cc/perf-run-config which recently graduated to master. It makes it possible to send perf results to a Codespeed server. See https://github.com/tobami/codespeed/ and web sites like http://speed.pypy.org/

Re: [PATCH] partial-clone: design doc

From: "Junio C Hamano" <gits...@pobox.com> "Philip Oakley" <philipoak...@iee.org> writes: + These filtered packfiles are incomplete in the traditional sense because + they may contain trees that reference blobs that the client does not have. Is a comment n

Re: [PATCH] partial-clone: design doc

From: "Jeff Hostetler" From: Jeff Hostetler First draft of design document for partial clone feature. Signed-off-by: Jeff Hostetler Signed-off-by: Jonathan Tan ---

Re: Re: Re: bug deleting "unmerged" branch (2.12.3)

ary could have definitions for "merged" and "fully merged" with manual pages referring to it. Thanks, I'll add your note to my list of clarifications. Philip Regards, Ulrich "Philip Oakley" <philipoak...@iee.org> schrieb am 08.12.2017 um 21:26 in Nachricht &

Re: What's cooking in git.git (Dec 2017, #02; Thu, 7)

From: "Christian Couder" On Thu, Dec 7, 2017 at 7:04 PM, Junio C Hamano wrote: * jh/object-filtering (2017-12-05) 9 commits (merged to 'next' on 2017-12-05 at 3a56b51085) + rev-list: support --no-filter argument +

Re: Re: bug deleting "unmerged" branch (2.12.3)

k or suggestions you could provide. -- Philip >>> "Philip Oakley" <philipoak...@iee.org> 04.12.17 0.30 Uhr >>> From: "Junio C Hamano" <gits...@pobox.com> > "Philip Oakley" <philipoak...@iee.org> writes: > >> I think it was t

Re: How hard would it be to implement sparse fetching/pulling?

From: "Jeff Hostetler" <g...@jeffhostetler.com> Sent: Monday, December 04, 2017 3:36 PM On 12/2/2017 11:30 AM, Philip Oakley wrote: From: "Jeff Hostetler" <g...@jeffhostetler.com> Sent: Friday, December 01, 2017 2:30 PM On 11/30/2017 8:51 PM, Vitaly Arbuzov w

Re: [RFE] Inverted sparseness (amended)

From: "Randall S. Becker" <rsbec...@nexbridge.com> On December 3, 2017 6:14 PM, Philip Oakley wrote a nugget of wisdom: From: "Randall S. Becker" <rsbec...@nexbridge.com> [...] If using the empty tree part doesn't pass muster (i.e. showing nothing isn't su

Re: [RFE] Inverted sparseness

From: "Randall S. Becker" :December 03, 2017 11:44 PM On December 3, 2017 6:14 PM, Philip Oakley wrote a nugget of wisdom: From: "Randall S. Becker" <rsbec...@nexbridge.com> Sent: Friday, December 01, 2017 6:31 PM On December 1, 2017 1:19 PM, Jeff Hostetler wro

Re: bug deleting "unmerged" branch (2.12.3)

From: "Junio C Hamano" <gits...@pobox.com> "Philip Oakley" <philipoak...@iee.org> writes: I think it was that currently you are on M, and neither A nor B are ancestors (i.e. merged) of M. As Junio said:- "branch -d" protects branches that ar

Re: [RFE] Inverted sparseness

From: "Randall S. Becker" Sent: Friday, December 01, 2017 6:31 PM On December 1, 2017 1:19 PM, Jeff Hostetler wrote: On 12/1/2017 12:21 PM, Randall S. Becker wrote: I recently encountered a really strange use-case relating to sparse clone/fetch that is really backwards

Re: Re: Unify annotated and non-annotated tags

From: "anatoly techtonik" comment at end - Philip On Fri, Nov 24, 2017 at 1:24 PM, Ævar Arnfjörð Bjarmason wrote: On Fri, Nov 24, 2017 at 10:52 AM, anatoly techtonik wrote: On Thu, Nov 23, 2017 at 6:08 PM, Randall S. Becker

Re: Re: bug deleting "unmerged" branch (2.12.3)

From: "Ulrich Windl" To: Cc: Sent: Wednesday, November 29, 2017 8:32 AM Subject: Antw: Re: bug deleting "unmerged" branch (2.12.3) "Ulrich Windl" writes: I think if more than

Re: Antw: Re: bug deleting "unmerged" branch (2.12.3)

Hi Ulrich From: "Johannes Schindelin" To: "Ulrich Windl" Cc: Sent: Wednesday, November 29, 2017 12:27 PM Subject: Re: Antw: Re: bug deleting "unmerged" branch (2.12.3) Hi Ulrich, On Wed, 29 Nov 2017,

Re: [add-default-config] add --default option to git config.

From: "Soukaina NAIT HMID" From: Soukaina NAIT HMID From a coursory read, there does need a bit more explanation. I see you also add a --color description and code, and don't say what the problem being solved is. If it is trickty to

Re: How hard would it be to implement sparse fetching/pulling?

From: "Jeff Hostetler" <g...@jeffhostetler.com> Sent: Friday, December 01, 2017 5:23 PM On 11/30/2017 6:43 PM, Philip Oakley wrote: From: "Vitaly Arbuzov" <v...@uber.com> [...] comments below.. On Thu, Nov 30, 2017 at 9:01 AM, Vitaly Arbuzov <v...@uber.co

Re: How hard would it be to implement sparse fetching/pulling?

Hi Jonathan, Thanks for the outline. It has help clarify some points and see the very similar alignments. The one thing I wasn't clear about is the "promised" objects/remote. Is that "promisor" remote a fixed entity, or could it be one of many remotes that could be a "provider"? (sort of

Re: How hard would it be to implement sparse fetching/pulling?

From: "Jeff Hostetler" Sent: Friday, December 01, 2017 2:30 PM On 11/30/2017 8:51 PM, Vitaly Arbuzov wrote: I think it would be great if we high level agree on desired user experience, so let me put a few possible use cases here. 1. Init and fetch into a new repo with

Re: How hard would it be to implement sparse fetching/pulling?

vel. (I'm hoping I've understood the dispersement of data between index and narrow packs corrrectly here ;-) -- Philip On Thu, Nov 30, 2017 at 3:43 PM, Philip Oakley <philipoak...@iee.org> wrote: From: "Vitaly Arbuzov" <v...@uber.com> Found some details here: https

Re: How hard would it be to implement sparse fetching/pulling?

From: "Vitaly Arbuzov" Found some details here: https://github.com/jeffhostetler/git/pull/3 Looking at commits I see that you've done a lot of work already, including packing, filtering, fetching, cloning etc. What are some areas that aren't complete yet? Do you need any help

Re: [PATCH v3 5/5] Testing: provide tests requiring them with ellipses after SHA-1 values

From: "Junio C Hamano" <gits...@pobox.com> "Philip Oakley" <philipoak...@iee.org> writes: From: "Junio C Hamano" <gits...@pobox.com> Ann T Ropea <bedhan...@gmx.de> writes: *1* We are being overly generous in t4013-diff-various.sh

Re: [PATCH] git-send-email: fix get_maintainer.pl regression

From: "Eric Sunshine" On Sat, Nov 18, 2017 at 9:54 PM, Eric Sunshine wrote: On Thu, Nov 16, 2017 at 10:48 AM, Alex Bennée wrote: +test_expect_success $PREREQ 'cc trailer with get_maintainer output' ' + [...] +

Re: [PATCH 6/7] builtin/describe.c: describe a blob

From: "Philip Oakley" <philipoak...@iee.org> s/with/without/ ... From: "Junio C Hamano" <gits...@pobox.com> : Friday, November 10, 2017 1:24 AM [catch up] "Philip Oakley" <philipoak...@iee.org> writes: From: "Stefan B

Re: [PATCH 6/7] builtin/describe.c: describe a blob

From: "Junio C Hamano" <gits...@pobox.com> : Friday, November 10, 2017 1:24 AM [catch up] "Philip Oakley" <philipoak...@iee.org> writes: From: "Stefan Beller" <sbel...@google.com> Rereading this discussion, there is currently no urgent thing to

Re: [PATCHv5 7/7] builtin/describe.c: describe a blob

From: "Stefan Beller" Sent: Thursday, November 16, 2017 2:00 AM [in catch up mode..] Sometimes users are given a hash of an object and they want to identify it further (ex.: Use verify-pack to find the largest blobs, but what are these? or [1]) When describing commits, we

Re: [PATCH v3 5/5] Testing: provide tests requiring them with ellipses after SHA-1 values

From: "Junio C Hamano" Ann T Ropea writes: *1* We are being overly generous in t4013-diff-various.sh because we do not want to destroy/take apart the here-document. Given that all this a temporary measure, we should get away with it. So, the need to

Re: more pedantry ... what means a file "known to Git"?

From: "Robert P. J. Day" apologies for more excruciating nitpickery, but i ask since it seems that phrase means slightly different things depending on where you read it. first, i assume that there are only two categories: 1) files known to Git 2) files unknown to

Re: [PATCH 00/30] Add directory rename detection to git

From: "Elijah Newren" <new...@gmail.com> : Friday, November 10, 2017 11:26 PM On Fri, Nov 10, 2017 at 2:27 PM, Philip Oakley <philipoak...@iee.org> wrote: From: "Elijah Newren" <new...@gmail.com> In this patchset, I introduce directory rename detectio

Re: [PATCH 00/30] Add directory rename detection to git

From: "Elijah Newren" [This series is entirely independent of my rename detection limits series. However, I have a separate rename detection performance series that depends on both this series and the rename detection limits series.] In this patchset, I introduce directory

Re: [PATCH 6/7] builtin/describe.c: describe a blob

From: "Stefan Beller" Rereading this discussion, there is currently no urgent thing to address? True. Then the state as announced by the last cooking email, to just cook it, seems about right and we'll wait for further feedback. Possibly only checking the documenation

Re: [PATCH 1/3] checkout: describe_detached_head: remove 3dots after committish

From: "Junio C Hamano" <gits...@pobox.com> Sent: Wednesday, November 08, 2017 1:59 AM "Philip Oakley" <philipoak...@iee.org> writes: But... ... This change causes quite a few tests to fall over; however, they all have truncated-something-longer-ellipses i

Re: [PATCH 1/3] checkout: describe_detached_head: remove 3dots after committish

From: "Ann T Ropea" Thanks for all the feedback provided! I'd like to summarise what consensus we have reached so far and then propose a way forward: * we'll use the term "ellipsis (pl. ellipses)" for what's been referred to as "3dots", "n-dots", "many dots" and so

Re: [PATCH 1/3] checkout: describe_detached_head: remove 3dots after committish

From: "Junio C Hamano" Ann T Ropea writes: This could be confusing not only for novices; in either case, no range should be insinuated by describe_detached_head. We actually do not insinuate any range in these output. These dots denote "truncated at

Re: [PATCH 6/7] builtin/describe.c: describe a blob

From: "Junio C Hamano" <gits...@pobox.com> Sent: Sunday, November 05, 2017 6:28 AM "Philip Oakley" <philipoak...@iee.org> writes: Is this not also an alternative case, relative to the user, for the scenario where the user has an oid/sha1 value but does not

Re: [PATCH 6/7] builtin/describe.c: describe a blob

From: "Junio C Hamano" Sent: Thursday, November 02, 2017 4:23 AM Junio C Hamano writes: The reason why we say "-ish" is "Yes we know v2.15.0 is *NOT* a commit object, we very well know it is a tag object, but because we allow it to be used in a context

  1   2   3   4   5   6   7   8   9   10   >