git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Philip Oakley <philipoakley@iee.org>
Cc: Jeff King <peff@peff.net>,
	Christian Couder <christian.couder@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] disable grafts during fetch/push/bundle
Date: Fri, 07 Mar 2014 00:29:37 +0100	[thread overview]
Message-ID: <531904E1.6010606@alum.mit.edu> (raw)
In-Reply-To: <08A515BA063C44E5A9EFC754793B2AD8@PhilipOakley>

On 03/07/2014 12:01 AM, Philip Oakley wrote:
> From: "Jeff King" <peff@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 that there would be a big demand for it.
>>>
>>> It's probably easier to wrap it than to explain to Windows users what
>>> they have to do.
>>
>> How would Windows users get a graft file in the first-place? There's no
>> GUI for it! ;)
> 
> Now, now... It's dead easy using the git-gui and Notepad++, you can see
> and confirm the sha1's, copy and paste, and the graft file is a very
> easy format, so even wimps (windows, icons, menus, pointers aka mouse)
> folks can do it. (It worked for me when I needed it ;-)

I didn't mean to insult all Windows users in general.  I was only
referring to the fact that since the default Windows command line is not
a POSIX shell, even an experienced Windows user might have trouble
figuring out how to execute a shell loop.  Putting this functionality in
a git command or script, by contrast, would make it work universally, no
fuss, no muss.

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/

  reply	other threads:[~2014-03-06 23:29 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 17:48 [PATCH] disable grafts during fetch/push/bundle Jeff King
2014-03-04 20:52 ` Junio C Hamano
2014-03-05  0:56   ` Jeff King
2014-03-05 18:49     ` Junio C Hamano
2014-03-05 18:52       ` Jeff King
2014-03-05 19:18         ` Junio C Hamano
2014-03-05 19:28           ` Jeff King
2014-03-05 20:24             ` Junio C Hamano
2014-03-06  8:42           ` Michael Haggerty
2014-03-06  9:17             ` Christian Couder
2014-03-06 15:56             ` Jeff King
2014-03-06 16:41               ` Michael Haggerty
2014-03-06 17:48                 ` Jeff King
2014-03-06 17:49                   ` [RFC/PATCH 1/4] replace: refactor command-mode determination Jeff King
2014-03-06 17:49                   ` [RFC/PATCH 2/4] replace: use OPT_CMDMODE to handle modes Jeff King
     [not found]                     ` <CAP8UFD2c0UKT8Uyw4j9SzKGx2oLn=o7N-dtvQHPaaBtLT6ggcw@mail.gmail.com>
2014-03-06 18:48                       ` Jeff King
2014-03-06 17:49                   ` [RFC/PATCH 3/4] replace: factor object resolution out of replace_object Jeff King
2014-03-06 17:51                   ` [RFC/PATCH 4/4] replace: add --edit option Jeff King
2014-03-07  1:57                     ` Eric Sunshine
2014-03-07 17:17                       ` Jeff King
2014-03-06 19:00                   ` [PATCH] disable grafts during fetch/push/bundle Junio C Hamano
2014-03-06 19:07                     ` Jeff King
2014-03-06 23:01                   ` Philip Oakley
2014-03-06 23:29                     ` Michael Haggerty [this message]
2014-03-06 23:39                       ` Junio C Hamano
2014-03-07  7:08                         ` Christian Couder
2014-03-07 17:19                           ` Jeff King
2014-03-19 22:39                             ` Junio C Hamano
2014-03-21  0:49                               ` Jeff King
2014-03-06 23:48                       ` Philip Oakley
2014-03-04 23:36 ` Eric Sunshine
2014-03-05  0:37   ` Jeff King
2014-03-05  1:00     ` Eric Sunshine
2014-03-05  1:05       ` Jeff King
2014-03-05  1:07         ` Eric Sunshine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=531904E1.6010606@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=philipoakley@iee.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).