Re: [PATCH 5/5] implement @{publish} shorthand

2014-01-09 Thread Philip Oakley
From: Jeff King p...@peff.net Sent: Wednesday, January 08, 2014 9:37 AM In a triangular workflow, you may have a distinct @{upstream} that you pull changes from, but publish by default (if you typed git push) to a different remote (or a different branch on the remote). One of the broader

[PATCH 4/6] Add deprecation note to old everyday.txt

2014-01-09 Thread Philip Oakley
Also include link to new man page. Signed-off-by: Philip Oakley philipoak...@iee.org --- Documentation/everyday.txt | 4 1 file changed, 4 insertions(+) diff --git a/Documentation/everyday.txt b/Documentation/everyday.txt index 2a18c1f..9de6347 100644 --- a/Documentation/everyday.txt +++ b

[PATCH 1/6] copy everyday.txt to giteveryday.txt

2014-01-09 Thread Philip Oakley
Signed-off-by: Philip Oakley philipoak...@iee.org --- Documentation/giteveryday.txt | 413 ++ 1 file changed, 413 insertions(+) create mode 100644 Documentation/giteveryday.txt diff --git a/Documentation/giteveryday.txt b/Documentation/giteveryday.txt new

[PATCH 6/6] Update git(1) link to giteveryday

2014-01-09 Thread Philip Oakley
Signed-off-by: Philip Oakley philipoak...@iee.org --- Documentation/git.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/git.txt b/Documentation/git.txt index aec3726..0e4875d 100644 --- a/Documentation/git.txt +++ b/Documentation/git.txt @@ -22,7 +22,7

[PATCH 2/6] Update giteveryday.txt to fit man page formatting

2014-01-09 Thread Philip Oakley
Add standard man page section titles. Also adjust anchor text markup for man page format. Signed-off-by: Philip Oakley philipoak...@iee.org --- Documentation/giteveryday.txt | 39 +++ 1 file changed, 27 insertions(+), 12 deletions(-) diff --git

[PATCH 3/6] add giteveryday to the manpages make list

2014-01-09 Thread Philip Oakley
Signed-off-by: Philip Oakley philipoak...@iee.org --- Documentation/Makefile | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/Makefile b/Documentation/Makefile index 91a12c7..7b745d0 100644 --- a/Documentation/Makefile +++ b/Documentation/Makefile @@ -23,6 +23,7 @@ MAN7_TXT

[PATCH 0/6] Make 'git help everyday' work

2014-01-09 Thread Philip Oakley
. The series could be squashed together once any foible have been eliminated. Philip Oakley (6): copy everyday.txt to giteveryday.txt Update giteveryday.txt to fit man page formatting add giteveryday to the manpages make list Add deprecation note to old everyday.txt add 'everyday' to the help

[PATCH 5/6] add 'everyday' to the help --guides list

2014-01-09 Thread Philip Oakley
Signed-off-by: Philip Oakley philipoak...@iee.org --- builtin/help.c | 1 + 1 file changed, 1 insertion(+) diff --git a/builtin/help.c b/builtin/help.c index cc17e67..45509ce 100644 --- a/builtin/help.c +++ b/builtin/help.c @@ -418,6 +418,7 @@ static struct { const char *help

Re: [PATCH 0/6] Make 'git help everyday' work

2014-01-10 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com I think we already use a nicer way to set up a page alias to keep old links working than making a copy in Documentation/; please mimic that if possible. This was mainly about ensuring that the 'git help' command could access these extra extra guides that

Re: [PATCH 0/6] Make 'git help everyday' work

2014-01-10 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Philip Oakley philipoak...@iee.org writes: From: Junio C Hamano gits...@pobox.com I think we already use a nicer way to set up a page alias to keep old links working than making a copy in Documentation/; please mimic that if possible. This was mainly

Re: [PATCH 0/6] Make 'git help everyday' work

2014-01-11 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Philip Oakley philipoak...@iee.org writes: From: Junio C Hamano gits...@pobox.com I think we already use a nicer way to set up a page alias to keep old links working than making a copy in Documentation/; please mimic that if possible. This was mainly

[PATCH v2] Make 'git help everyday' work

2014-01-12 Thread Philip Oakley
to the manpages make list. Deprecate the old everyday.txt as *.txto in the same manner as bd4a3d61 (Rename {git- = git}remote-helpers.txt, 2013-01-31), including a link to the new man page. Add 'everyday' to the help --guides list. Update git(1) and 5 other links to giteveryday. Signed-off-by: Philip

[PATCH] Provide a 'git help user-manual' route to the docbook

2014-01-15 Thread Philip Oakley
Signed-off-by: Philip Oakley philipoak...@iee.org --- Documentation/Makefile | 1 + Documentation/gituser-manual.txt | 34 ++ builtin/help.c | 1 + 3 files changed, 36 insertions(+) create mode 100644 Documentation/gituser-manual.txt

[PATCH] provide a Git user-manual man page

2014-01-15 Thread Philip Oakley
. This patch is based on master, so the update to the help.c list of guides may need a simple merge resolution with the 'git help everyday' patch currently in pu. Philip Oakley (1): Provide a 'git help user-manual' route to the docbook Documentation/Makefile | 1 + Documentation

Re: [PATCH 0/6] Make 'git help everyday' work - relnotes

2014-01-16 Thread Philip Oakley
From: Stefan Näwe stefan.na...@atlas-elektronik.com [...] I'd really like to see 'git help relnotes' working as well... Stefan Stefan, Were you thinking that all the release notes would be quoted verbatim in the one long man page? Or that it would be a set of links to each of the

Re: [PATCH v4 6/6] Documentation: Describe 'submodule update' modes in detail

2014-01-16 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com W. Trevor King wk...@tremily.us writes: [...] @@ -155,13 +155,31 @@ it contains local modifications. update:: Update the registered submodules, i.e. clone missing submodules and - checkout the commit specified in the index of the containing

Re: [PATCH 0/6] Make 'git help everyday' work - relnotes

2014-01-21 Thread Philip Oakley
From: Stefan Näwe stefan.na...@atlas-elektronik.com Am 16.01.2014 22:14, schrieb Philip Oakley: From: Stefan Näwe stefan.na...@atlas-elektronik.com [...] I'd really like to see 'git help relnotes' working as well... Stefan Stefan, Were you thinking that all the release notes would

Re: [PATCH 0/6] Make 'git help everyday' work - relnotes

2014-01-21 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Philip Oakley philipoak...@iee.org writes: Determining which is the current release note is possibly more problematic, which should be when making the documentation. Hmmm Why? You are already aware of the stale-notes section, no? Isn't the top one

Re: [PATCH 0/6] Make 'git help everyday' work - relnotes

2014-01-22 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Philip Oakley philipoak...@iee.org writes: I already have a local patch that creates a stalenote.txt file, and includes that in a release-notes(7) man page, but it still leaves the actual release notes in a separate plain text file, linked from the man

Re: C standard compliance?

2014-01-29 Thread Philip Oakley
From: David Kastrup d...@gnu.org Junio C Hamano gits...@pobox.com writes: David Kastrup d...@gnu.org writes: Hi, I am wondering if I may compare pointers with that have been created using different calls of malloc. The C standard does not allow this (inequalities are only allowed for

Re: What's cooking in git.git (Jan 2014, #06; Wed, 29)

2014-01-30 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com * po/everyday-doc (2014-01-27) 1 commit - Make 'git help everyday' work This may make the said command to emit something, My initial intention ;-) but the source is not meant to be formatted into a manual pages to begin with, and also its

Re: [RFC/PATCH] howto/maintain-git.txt: new version numbering scheme

2014-02-03 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Sent: Friday, January 31, 2014 11:14 PM We wanted to call the upcoming release Git 1.9, with its maintenance track being Git 1.9.1, Git 1.9.2, etc., but various third-party tools are reported to assume that there are at least three dewey-decimal components

Re: [RFC/PATCH] howto/maintain-git.txt: new version numbering scheme

2014-02-04 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Philip Oakley philipoak...@iee.org writes: If we are progressing from V1.9 to V2.0 quickly (one cycle?), which I understand is the plan, then mixing the minor development items (patch series which progress to master) with the maintenance fixes over

Re: [PATCH] blame.c: prepare_lines should not call xrealloc for every line

2014-02-04 Thread Philip Oakley
From: David Kastrup d...@gnu.org To: Junio C Hamano gits...@pobox.com Cc: git@vger.kernel.org Sent: Tuesday, February 04, 2014 9:09 PM Subject: Re: [PATCH] blame.c: prepare_lines should not call xrealloc for every line Junio C Hamano gits...@pobox.com writes: Junio C Hamano

Re: [PATCH] blame.c: prepare_lines should not call xrealloc for every line

2014-02-04 Thread Philip Oakley
From: Philip Oakley philipoak...@iee.org From: David Kastrup d...@gnu.org To: Junio C Hamano gits...@pobox.com Cc: git@vger.kernel.org Sent: Tuesday, February 04, 2014 9:09 PM Subject: Re: [PATCH] blame.c: prepare_lines should not call xrealloc for every line [...] Where's the difference

Re: [PATCH v3 8/9] rebase: add the --gpg-sign option

2014-02-08 Thread Philip Oakley
On 07/02/14 23:50, brian m. carlson wrote: On Mon, Feb 03, 2014 at 01:42:06PM -0800, Junio C Hamano wrote: + --gpg-sign) + gpg_sign_opt=-S + ;; + --gpg-sign=*) + # Try to quote only the argument, as this will appear in human-readable +

[PATCH] [PATCH] Provide a release-notes man page / guide

2014-02-15 Thread Philip Oakley
Use the symlinked RelNote file as a list-block to act as the core of the release-notes man page. The mantainers work load should not be affected. Signed-off-by: Philip Oakley philipoak...@iee.org --- The included lines are inset 11 spaces by the man page asciidoc formatting so some are more

[PATCH] provide a Git user-manual man page

2014-02-15 Thread Philip Oakley
directly accessible via the usual 'git help guide' command. This patch provides a simple man page with onward links to the true User-Manual. The man page is based directly on a very cut down version of the git(1) page. This patch is based on 1.9.0 master. Philip Oakley (1): Provide a 'git help

[PATCH] Provide a 'git help user-manual' route to the docbook

2014-02-15 Thread Philip Oakley
Signed-off-by: Philip Oakley philipoak...@iee.org --- Documentation/Makefile | 1 + Documentation/gituser-manual.txt | 34 ++ builtin/help.c | 1 + 3 files changed, 36 insertions(+) create mode 100644 Documentation/gituser-manual.txt

Re: [PATCH] Provide a 'git help user-manual' route to the docbook

2014-02-18 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Philip Oakley philipoak...@iee.org writes: diff --git a/Documentation/gituser-manual.txt b/Documentation/gituser-manual.txt new file mode 100644 index 000..9fd4744 --- /dev/null +++ b/Documentation/gituser-manual.txt @@ -0,0 +1,34 @@ +gituser-manual

Re: [PATCH] Git release notes man page

2014-02-18 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Philip Oakley philipoak...@iee.org writes: A few days too late for the 1.9.0 release cycle :( This responds to Stefan Nwe's request for a 'git help' command that would access the release notes. ($gmane/240595 17 Jan 2014). I've used the full name

Re: [PATCH] help: include list of aliases in git-help --all

2014-02-25 Thread Philip Oakley
From: Joel Nothman joel.noth...@gmail.com On 26 February 2014 06:15, Junio C Hamano gits...@pobox.com wrote: Joel Nothman joel.noth...@gmail.com writes: Git help --all had listed all git commands, but no configured aliases. This includes aliases as a separate listing, after commands in the

Re: [PATCH v3 10/25] Add new environment variable $GIT_COMMON_DIR

2014-02-26 Thread Philip Oakley
From: Duy Nguyen pclo...@gmail.com On Wed, Feb 26, 2014 at 8:24 AM, Eric Sunshine sunsh...@sunshineco.com wrote: +'GIT_COMMON_DIR':: + If this variable is set to a path, non-worktree files that are + normally in $GIT_DIR will be taken from this path + instead.

Re: Compiling git for Windows

2014-02-26 Thread Philip Oakley
From: Robert Dailey rcdailey.li...@gmail.com Oddly I'm not able to find any instructions on how to build Git for Windows. I've done a clone of the repository here: https://github.com/msysgit/git I did attempt to try doing it myself. I installed 'make' and mingw-gcc in Cygwin and attempted

How to mark a complete sub-directory assume-unchanged/skip-worktree?

2014-02-27 Thread Philip Oakley
to look at marking sub-dirs as --skip-worktree, or some other sentinel value for the missing tree? --- Philip Oakley -- 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

Re: [PATCH] GSoC2014 microprojects #6 Change bundle.c:add_to_ref_list() to use ALLOC_GROW()

2014-02-27 Thread Philip Oakley
From: Sun He sunheeh...@gmail.com Signed-off-by: Sun He sunheeh...@gmail.com --- bundle.c |6 +- 1 files changed, 1 insertions(+), 5 deletions(-) diff --git a/bundle.c b/bundle.c index 7809fbb..1a7b7eb 100644 --- a/bundle.c +++ b/bundle.c @@ -14,11 +14,7 @@ static const char

Re: How to mark a complete sub-directory assume-unchanged/skip-worktree?

2014-02-27 Thread Philip Oakley
From: Duy Nguyen pclo...@gmail.com On Fri, Feb 28, 2014 at 12:25 AM, Philip Oakley philipoak...@iee.org wrote: Have there been previous attempts to look at marking sub-dirs as --skip-worktree, or some other sentinel value for the missing tree? I dealt with this by creating partial index

Re: How to mark a complete sub-directory assume-unchanged/skip-worktree?

2014-02-28 Thread Philip Oakley
From: Duy Nguyen pclo...@gmail.com On Fri, Feb 28, 2014 at 6:46 AM, Philip Oakley philipoak...@iee.org wrote: Is there a particular bit of code I'd be worth studying for the partial index example to see how well it might fit my ideas? My last attempt was http://git.661346.n2.nabble.com/PATCH

Re: [PATCH/RFC] rebase: new convenient option to edit a single commit

2014-02-28 Thread Philip Oakley
From: Jeff King p...@peff.net I'd expect -$n to mean rebase the last $n commits (as opposed to everything not in the upstream). That does not work currently, of course, but: 1. It has the potential to confuse people who read it, since it's unlike what -1 means in most of the rest of git.

Re: [PATCH] Replace memcpy with hashcpy when lengths defined

2014-03-02 Thread Philip Oakley
From: Alberto albco...@gmail.com From: Alberto Corona albco...@gmail.com Replaced memcpy with hashcpy where lengts in memcpy s/lengts/lengths/ are already defined. Signed-off-by: Alberto Corona albco...@gmail.com --- bundle.c| 2 +- grep.c | 2 +- refs.c | 2 +- sha1_name.c | 4

Re: [PATCH 1/2] test-lib: tests skipped by GIT_SKIP_TESTS say so

2014-03-03 Thread Philip Oakley
From: Ilya Bobyr ilya.bo...@gmail.com We used to show (missing ) next to tests skipped because they are specified in GIT_SKIP_TESTS. Use (matched by GIT_SKIP_TESTS) instead. The message below forgets the by. Otherwise looks sensible. --- t/test-lib.sh | 13 - 1 files changed,

Re: [PATCH 2/2] test-lib: GIT_TEST_ONLY to run only specific tests

2014-03-03 Thread Philip Oakley
Minor nits. From: Ilya Bobyr ilya.bo...@gmail.com This is a counterpart to GIT_SKIP_TESTS. Mostly useful when debugging. --- t/README | 15 +++ t/test-lib.sh |8 2 files changed, 23 insertions(+), 0 deletions(-) diff --git a/t/README b/t/README index

Re: My advice for GSoC applicants

2014-03-03 Thread Philip Oakley
they be included? - which points needed repeating often, and why? Where was the disconnect? - what would a patch look like... Philip Oakley [1] README; INSTALL; Documentation/SubmittingPatches; Documentation/CodingGuidelines; -- To unsubscribe from this list: send the line unsubscribe git in the body

Re: [PATCH] disable grafts during fetch/push/bundle

2014-03-06 Thread Philip Oakley
From: Michael Haggerty mhag...@alum.mit.edu On 03/07/2014 12:01 AM, Philip Oakley wrote: From: Jeff King p...@peff.net On Thu, Mar 06, 2014 at 05:41:27PM +0100, Michael Haggerty wrote: We can wrap that in git replace --convert-grafts, but I do not think grafts are so common

Re: [PATCH 3/7] test patch hunk editing with commit -p -m

2014-03-10 Thread Philip Oakley
mincro nit. From: Benoit Pierre benoit.pie...@gmail.com Add (failing) test: with commit changing the environment to let hooks now that no editor will be used (by setting GIT_EDITOR to :), the s/now/know/ edit hunk functionality does not work (no editor is launched and the whole hunk is

Re: What's cooking in git.git (Mar 2014, #03; Fri, 14)

2014-03-16 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com -- [Stalled] ... * po/everyday-doc (2014-01-27) 1 commit - Make 'git help everyday' work This may make the said command to emit something, but the source is not meant to be formatted into a manual pages to

Should 'git reset --hard' keep a stashed backup?

2014-03-16 Thread Philip Oakley
A bike-shedding thought: Many inexperienced users do a 'git reset --hard' only to discover they have deleted something important and want it back. (e.g. git-users yesterday [1]) One possible option is that Git could stash the current work-tree contents (git stash create) into a commit and

Re: What's cooking in git.git (Mar 2014, #03; Fri, 14)

2014-03-17 Thread Philip Oakley
From: Ramkumar Ramachandra artag...@gmail.com Philip Oakley wrote: * po/everyday-doc (2014-01-27) 1 commit - Make 'git help everyday' work This may make the said command to emit something, but the source is not meant to be formatted into a manual pages to begin with, and also its contents

Re: What's cooking in git.git (Mar 2014, #03; Fri, 14)

2014-03-17 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Philip Oakley philipoak...@iee.org writes: * po/git-help-user-manual (2014-02-18) 1 commit - Provide a 'git help user-manual' route to the docbook I am not sure if this is even needed. My rhetorical question would be what should 'git help user-manual

Re: git log omits deleting merges

2014-03-20 Thread Philip Oakley
From: Jeff King p...@peff.net On Thu, Feb 20, 2014 at 08:35:33AM +0100, Ephrim Khong wrote: Hi, git log seems to omit merge commits that delete a file if --follow or --diff-filter=D is given. Below is a testcase. I'm not sure if it is desired behaviour for --diff-filter=D, but it's probably

Re: Bug report: git add . -p Argument list too long

2014-03-31 Thread Philip Oakley
- Original Message - From: Dieter Komendera die...@komendera.com To: git@vger.kernel.org Sent: Monday, March 31, 2014 10:04 PM Subject: Bug report: git add . -p Argument list too long Hi there, since a while when I want to stage diffs in one of my big repos with git add . -p” I get

Re: What's cooking in git.git (Apr 2014, #01; Fri, 4)

2014-04-06 Thread Philip Oakley
Junio C Hamano gits...@pobox.com wrote in message news:xmqq4n28q0ad@gitster.dls.corp.google.com... Here are the topics that have been cooking. ... * po/everyday-doc (2014-01-27) 1 commit - Make 'git help everyday' work This may make the said command to emit something, but the source

Re: Silly time stamps

2014-04-11 Thread Philip Oakley
From: Holger Hellmuth hellm...@ira.uka.de To: Michael Haggerty mhag...@alum.mit.edu Cc: Mahmoud Asshole a1209...@drdrb.net; git@vger.kernel.org If you look at Mahmoud's email address, it is from http://10minutemail.com/ 'the best disposable e-mail service.'. So it looks like s/he knew what

Re: What's cooking in git.git (Apr 2014, #08; Fri, 25)

2014-04-26 Thread Philip Oakley
From: Felipe Contreras felipe.contre...@gmail.com My conclusion is based on logic and reason, you forget And repeatable measurement / evidence which are the bedstone of science. You can make sensible decisions based on

Re: [PATCH 10/12] MINGW: config.mak.uname: drop USE_NED_ALLOCATOR

2014-04-28 Thread Philip Oakley
From: Felipe Contreras felipe.contre...@gmail.com Marat Radchenko wrote: nedalloc was initially added in f0ed82 to fix slowness of standard WinXP memory allocator. Since WinXP is EOLed, this point is no longer valid. The fact that WinXP is EOLed doesn't mean people are not using it any more

Re: [PATCH v5 1/6] pull: rename pull.rename to pull.mode

2014-04-29 Thread Philip Oakley
From: Felipe Contreras felipe.contre...@gmail.com Also 'branch.name.rebase' to 'branch.name.pullmode'. Sorry I haven't commented earlier. Because the 0/6 explanation isn't a commit, a few extra words would be useful to capture what the 0/6 cover letter said to start the patch series

Re: [PATCH v5 1/6] pull: rename pull.rename to pull.mode

2014-04-29 Thread Philip Oakley
From: Felipe Contreras felipe.contre...@gmail.com Philip Oakley wrote: From: Felipe Contreras felipe.contre...@gmail.com Also 'branch.name.rebase' to 'branch.name.pullmode'. Sorry I haven't commented earlier. Because the 0/6 explanation isn't a commit, a few extra words would be useful

Re: Pull is Evil

2014-05-01 Thread Philip Oakley
From: Marc Branchaud marcn...@xiplink.com Sent: Wednesday, April 30, 2014 8:45 PM [...] I don't think we'll ever be able to create a One Git Pull To Rule Them All. At best we'll end up with something with enough knobs that it could be configured to work in most workflows (I think we're actually

Re: Pull is Evil

2014-05-01 Thread Philip Oakley
Oops.. From: Philip Oakley philipoak...@iee.org From: Marc Branchaud marcn...@xiplink.com Sent: Wednesday, April 30, 2014 8:45 PM [...] I don't think we'll ever be able to create a One Git Pull To Rule Them All. At best we'll end up with something with enough knobs that it could be configured

Re: Pull is Mostly Evil

2014-05-02 Thread Philip Oakley
From: David Kastrup d...@gnu.org Marc Branchaud marcn...@xiplink.com writes: To that end, I suggest that pull's default behaviour should be to do *nothing*. It should just print out a message to the effect that it hasn't been configured, and that the user should run git help pull for

Re: Pull is Mostly Evil

2014-05-02 Thread Philip Oakley
From: Marc Branchaud marcn...@xiplink.com Sent: Friday, May 02, 2014 4:37 PM (Apologies for not CCing all the folks who've participated in the Pull is Evil thread -- I couldn't find a good branch of that thread for this message.) OK, so maybe git pull is just Mostly Evil. People seem to have

Re: Pull is Mostly Evil

2014-05-02 Thread Philip Oakley
From: Felipe Contreras felipe.contre...@gmail.com Sent: Friday, May 02, 2014 8:05 PM Philip Oakley wrote: From: David Kastrup d...@gnu.org Marc Branchaud marcn...@xiplink.com writes: To that end, I suggest that pull's default behaviour should be to do *nothing*. It should just print out

Re: Pull is Mostly Evil

2014-05-03 Thread Philip Oakley
From: Felipe Contreras felipe.contre...@gmail.com Sent: Saturday, May 03, 2014 12:23 AM Philip Oakley wrote: From: Felipe Contreras felipe.contre...@gmail.com So? No defaults can please absolutely everyone, the best anybody can do is try to please the majority of people, and merging fast

Re: Pull is Mostly Evil

2014-05-03 Thread Philip Oakley
From: Jonathan Nieder jrnie...@gmail.com Sent: Friday, May 02, 2014 11:53 PM Hi, Philip Oakley wrote: That assumes that [git pull] doing something is better than doing nothing, which is appropriate when the costs on either side are roughly similar. I think the conversation's going around

Re: What's cooking in git.git (Apr 2014, #08; Fri, 25)

2014-05-09 Thread Philip Oakley
From: Michael Haggerty mhag...@alum.mit.edu On 04/26/2014 01:19 AM, Jeff King wrote: On Fri, Apr 25, 2014 at 03:50:26PM -0700, Junio C Hamano wrote: [...] * fc/publish-vs-upstream (2014-04-21) 8 commits - sha1_name: add support for @{publish} marks - sha1_name: simplify track finding -

Re: [git-users] worlds slowest git repo- what to do?

2014-05-15 Thread Philip Oakley
From: John Fisher fishook2...@gmail.com I assert based on one piece of evidence ( a post from a facebook dev) that I now have the worlds biggest and slowest git repository, and I am not a happy guy. I used to have the worlds biggest CVS repository, but CVS can't handle multi-G sized files. So I

Re: [PATCH v2 1/1] doc: format-patch: don't use origin as a branch name

2014-08-14 Thread Philip Oakley
resending - send mail failure - Original Message - From: Philip Oakley philipoak...@iee.org To: Junio C Hamano gits...@pobox.com Cc: GitList git@vger.kernel.org; Jonathan Nieder jrnie...@gmail.com Sent: Wednesday, August 13, 2014 5:03 PM Subject: Re: [PATCH v2 1/1] doc: format-patch

Re: [PATCH v2] teach fast-export an --anonymize option

2014-08-22 Thread Philip Oakley
From: Jeff King p...@peff.net: Friday, August 22, 2014 12:21 AM On Thu, Aug 21, 2014 at 06:49:10PM -0400, Jeff King wrote: The few things I don't anonymize are: 1. ref prefixes. We see the same distribution of refs/heads vs refs/tags, etc. 2. refs/heads/master is left untouched, for

[PATCH v3 3/3] Make 'git help everyday' work

2014-09-29 Thread Philip Oakley
well with AsciiDoc as a man page and refreshed content to a more command modern style. Add 'everyday' to the help --guides list and update git(1) and 5 other links to giteveryday. Signed-off-by: Philip Oakley philipoak...@iee.org --- Documentation/Makefile | 3 +- Documentation

[PATCH v3 0/3] Make 'git help everyday' work

2014-09-29 Thread Philip Oakley
v2] Make 'git help everyday' work Philip Oakley (3): doc: modernise everyday.txt wording and format in man page style doc: Makefile regularise OBSOLETE_HTML list building Make 'git help everyday' work Documentation/Makefile | 6 +- Documentation/everyday.txt | 413

[PATCH v3 2/3] doc: Makefile regularise OBSOLETE_HTML list building

2014-09-29 Thread Philip Oakley
Helped-by: Junio C Hamano gits...@pobox.com Signed-off-by: Philip Oakley philipoak...@iee.org --- Documentation/Makefile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/Makefile b/Documentation/Makefile index cea0e7a..3b56714 100644 --- a/Documentation/Makefile

[PATCH v3 1/3] doc: modernise everyday.txt wording and format in man page style

2014-09-29 Thread Philip Oakley
Helped-by: Junio C Hamano gits...@pobox.com Signed-off-by: Philip Oakley philipoak...@iee.org --- Documentation/everyday.txt | 246 ++--- 1 file changed, 140 insertions(+), 106 deletions(-) diff --git a/Documentation/everyday.txt b/Documentation

[PATCH v4 3/3] Make 'git help everyday' work

2014-10-10 Thread Philip Oakley
well with AsciiDoc as a man page and refreshed content to a more command modern style. Add 'everyday' to the help --guides list and update git(1) and 5 other links to giteveryday. Signed-off-by: Philip Oakley philipoak...@iee.org --- Documentation/Makefile | 3 +- Documentation

[PATCH v4 2/3] doc: Makefile regularise OBSOLETE_HTML list building

2014-10-10 Thread Philip Oakley
Helped-by: Junio C Hamano gits...@pobox.com Signed-off-by: Philip Oakley philipoak...@iee.org --- Documentation/Makefile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/Makefile b/Documentation/Makefile index cea0e7a..3b56714 100644 --- a/Documentation/Makefile

[PATCH v4 0/3] Make 'git help everyday' work

2014-10-10 Thread Philip Oakley
: Junio C Hamano gits...@pobox.com Sent: Tuesday, September 30, 2014 12:24 AM Subject: Re: [PATCH v3 1/3] doc: modernise everyday.txt wording and format in man page style Philip Oakley philipoak...@iee.org writes: @@ -45,7 +58,7 @@ following commands. * linkgit:git-rebase[1] to maintain

[PATCH v4 1/3] doc: modernise everyday.txt wording and format in man page style

2014-10-10 Thread Philip Oakley
Helped-by: Junio C Hamano gits...@pobox.com Signed-off-by: Philip Oakley philipoak...@iee.org --- Documentation/everyday.txt | 260 ++--- 1 file changed, 151 insertions(+), 109 deletions(-) diff --git a/Documentation/everyday.txt b/Documentation

Re: [PATCH v4 0/3] Make 'git help everyday' work

2014-10-11 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Thanks. Looked alright from a cursory read; I tweaked s/10/-10/ where you gave examples of limiting output from git log before queuing. That was my mis-reading. I'd even noticed that it looked 'different' but just didn't see the leading '-' when checking

Re: [PATCH 0/4] Allow building Git with Asciidoctor

2014-10-16 Thread Philip Oakley
From: brian m. carlson sand...@crustytoothpaste.net This series is designed to implement the changes necessary to build Git using Asciidoctor instead of AsciiDoc. [..] Even with these patches, Asciidoctor warns about everyday.txt and user-manual.txt. I'm not sending patches for these right

Re: git-bundle rev handling and de-duping

2014-10-17 Thread Philip Oakley
From: Jeff King p...@peff.net [subject tweaked as we have veered quite far off the original, and this might get more attention from interested people] On Thu, Oct 16, 2014 at 10:39:54AM -0700, Junio C Hamano wrote: 2. We use object_array_remove_duplicates() to de-dup git bundle create

[PATCH] doc: fix 'git status --help' character quoting

2014-10-19 Thread Philip Oakley
Correct backtick quoting for some of the modification states to give consistent web rendering. While at it, use 00 for ASCII NUL to avoid any confusion with the letter O. Signed-off-by: Philip Oakley philipoak...@iee.org --- Noticed when reviewing a stackoverflow problem where the OP actually

Re: [PATCH] doc: fix 'git status --help' character quoting

2014-10-20 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Philip Oakley philipoak...@iee.org writes: Correct backtick quoting for some of the modification states to give consistent web rendering. This is to match the way how XY PATH1 - PATH2 is typeset, I presume. Some in the body text are already `XY

Re: [PATCH] doc: fix 'git status --help' character quoting

2014-10-20 Thread Philip Oakley
From: Philip Oakley philipoak...@iee.org From: Junio C Hamano gits...@pobox.com Philip Oakley philipoak...@iee.org writes: .. While at it, use 00 for ASCII NUL to avoid any confusion with the letter O. (remember its quotation is consumed by ascidoc) looked too much like an I mis

Re: [PATCH] doc: fix 'git status --help' character quoting

2014-10-20 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Philip Oakley philipoak...@iee.org writes: From: Junio C Hamano gits...@pobox.com Philip Oakley philipoak...@iee.org writes: ... [ (ASCII 0) change] The reason I proposed the change is because on the web view, on my machine, I questioned whether

Re: [PATCH] doc: fix 'git status --help' character quoting

2014-10-21 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Junio C Hamano gits...@pobox.com writes: Philip Oakley philipoak...@iee.org writes: From: Junio C Hamano gits...@pobox.com ... I think it is just the font. I just opened the above page with Chrome and futzed the text from '0' to '0123456789' to see how

[PATCH] doc: 'git status' quote the zero (NUL) character

2014-10-21 Thread Philip Oakley
Newer web rendering of 'git status --help --web' shows the zero in NUL (ASCII 0) as if it is a small 'o' character. Back-tick quote the zero to ensure it is displayed as a full size mono-spaced font. Also display the double quote (ASCII 34) in the same manner. Signed-off-by: Philip Oakley

Re: [PATCH] use child_process_init() to initialize struct child_process variables

2014-10-30 Thread Philip Oakley
From: Jeff King p...@peff.net On Wed, Oct 29, 2014 at 12:16:05PM -0700, Junio C Hamano wrote: Probably three helper functions: - The first is to find tops and bottoms (this translates fuzzy specifications such as --since 30.days into a more concrete revision range ^A ^B ... Z to

Re: [PATCH] use child_process_init() to initialize struct child_process variables

2014-11-02 Thread Philip Oakley
From: Jeff King p...@peff.net On Fri, Oct 31, 2014 at 02:48:17PM -0700, Junio C Hamano wrote: Programs that read a pack data stream unpack-objects were originally designed to ignore cruft after the pack data stream ends, and because the bundle file format ends with pack data stream, you should

Re: [PATCH] use child_process_init() to initialize struct child_process variables

2014-11-05 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Sent: Monday, November 03, 2014 11:42 PM Jeff King p...@peff.net writes: I peeked at libgit2 and I think it does not support bundles at all yet, so that is safe. Grepping for bundle in dulwich turns up no hits, either. Looks like JGit does support them.

Re: [PATCH] use child_process_init() to initialize struct child_process variables

2014-11-05 Thread Philip Oakley
From: Jeff King p...@peff.net Subject: Re: [PATCH] use child_process_init() to initialize struct child_process variables On Tue, Nov 04, 2014 at 01:56:15PM -0800, Junio C Hamano wrote: 2. Including two lines, like: $sha1 HEAD\0symref=refs/heads/master $sha1 HEAD

Re: [PATCH] use child_process_init() to initialize struct child_process variables

2014-11-05 Thread Philip Oakley
From: Jeff King p...@peff.net On Wed, Nov 05, 2014 at 01:35:21PM -, Philip Oakley wrote: 2. Including two lines, like: [...] I believe that the 'two HEADs' mechanism would also fall foul of the 'duplicate refs' warning (untested). It didn't in my very brief testing of what I posted

Re: [PATCH] Fix some sparse warnings

2013-07-16 Thread Philip Oakley
From: Jeff King p...@peff.net Sent: Tuesday, July 16, 2013 7:21 AM On Tue, Jul 16, 2013 at 07:57:20AM +0200, Johannes Sixt wrote: Am 7/15/2013 19:31, schrieb Ramsay Jones: Sparse issues three Using plain integer as NULL pointer warnings. Each warning relates to the use of an '{0}'

Re: [PATCH] Fix some sparse warnings

2013-07-16 Thread Philip Oakley
On 16/07/13 22:18, Stefan Beller wrote: On 07/16/2013 10:53 PM, Philip Oakley wrote: From: Jeff King p...@peff.net Sent: Tuesday, July 16, 2013 7:21 AM On Tue, Jul 16, 2013 at 07:57:20AM +0200, Johannes Sixt wrote: Am 7/15/2013 19:31, schrieb Ramsay Jones: Sparse issues three Using plain

Re: Git Clone Parameter

2013-07-19 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Sent: Friday, July 19, 2013 4:02 PM Allan Acheampong allanad...@gmail.com writes: ... I'm new to git, but I found it very confusing to understand the difference between remote , remotes. Is it in the cloned repo, or is it in a remote place? If its local,

Re: [PATCH v2 05/16] fetch-pack: support fetching from a shallow repository

2013-07-22 Thread Philip Oakley
From: Nguyễn Thái Ngọc Duy pclo...@gmail.com upload-pack already advertises all shallow grafts if server repository is shallow. This information can be used to add more grafts to the client if the server sends commit chains down to its graft points. If the server is shallow, before we receive

Re: [PATCH v2 15/16] config: add core.noshallow to prevent turning a repo into a shallow one

2013-07-22 Thread Philip Oakley
From: Nguyễn Thái Ngọc Duy pclo...@gmail.com Subject: [PATCH v2 15/16] config: add core.noshallow to prevent turning a repo into a shallow one Surely this should be the default now that it is possible to corrupt a golden repo by pushing/fetching a shallow repository to it and it then becomes

Re: [PATCH v2 00/16] First class shallow clone

2013-07-22 Thread Philip Oakley
From: Nguyễn Thái Ngọc Duy pclo...@gmail.com Subject: [PATCH v2 00/16] First class shallow clone It's nice to see that shallow can be a first class clone. Thinking outside the box, does this infrastructure offer the opportunity to maybe add a date based depth option that would establish the

Re: [PATCH v2 15/16] config: add core.noshallow to prevent turning a repo into a shallow one

2013-07-23 Thread Philip Oakley
From: Duy Nguyen pclo...@gmail.com Sent: Tuesday, July 23, 2013 2:28 AM On Tue, Jul 23, 2013 at 2:23 AM, Philip Oakley philipoak...@iee.org wrote: From: Nguyễn Thái Ngọc Duy pclo...@gmail.com Subject: [PATCH v2 15/16] config: add core.noshallow to prevent turning a repo into a shallow one

Re: [PATCH v3 0/6]

2013-07-23 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Sent: Tuesday, July 23, 2013 7:26 PM Jakub Narebski jna...@gmail.com writes: Junio C Hamano gitster at pobox.com writes: This is mostly unchanged since the previous round, except that * The option is spelled --force-with-lease=ref:expect. Nobody

Re: [PATCH v2 00/16] First class shallow clone

2013-07-23 Thread Philip Oakley
From: Duy Nguyen pclo...@gmail.com Sent: Tuesday, July 23, 2013 2:20 AM On Tue, Jul 23, 2013 at 6:41 AM, Philip Oakley philipoak...@iee.org wrote: From: Nguyễn Thái Ngọc Duy pclo...@gmail.com Subject: [PATCH v2 00/16] First class shallow clone It's nice to see that shallow can be a first class

Re: [PATCH v2 00/16] First class shallow clone

2013-07-24 Thread Philip Oakley
From: Duy Nguyen pclo...@gmail.com Sent: Wednesday, July 24, 2013 2:57 AM On Wed, Jul 24, 2013 at 5:33 AM, Philip Oakley philipoak...@iee.org wrote: In some sense a project with a sub-module is a narrow clone, split at a 'commit' object. Yes, except narrow clone is more flexible. You have

  1   2   3   4   5   6   7   8   9   10   >