From: Sitaram Chamarty <sitaramc@gmail.com>
To: Sheldon Els <sheldon@easyfundraising.org.uk>
Cc: git@vger.kernel.org
Subject: Re: git feature-branch
Date: Fri, 25 Jul 2014 11:39:44 +0530 [thread overview]
Message-ID: <53D1F4A8.4050509@gmail.com> (raw)
In-Reply-To: <CAJnDmGLaXPFYSVteehdz66C-kiDcBpAkQpW-uX8x-s9Qe_+kNA@mail.gmail.com>
On 07/25/2014 11:10 AM, Sheldon Els wrote:
> It is just a shell script yes, and a man page to make things a bit
> more discoverable for "git help feature-branch".
>
> The brew command comes from homebrew, a popular OSX package manager.
> My platform of choice.
You might want to at least add "these instructions are for people using
macs". Otherwise it seems like you assume everyone is using macs, and
nothing else exists in the world as far as you are concerned.
> Perhaps I can get support for an easy install for your platform. Do
When I said "more generic" I meant "it's just *one* shell script; put it
somewhere on your $PATH". That should be sufficient for something like
this (at the risk of going a bit off-topic for the list).
> you think a Makefile that installs to /usr/local/bin and
> /usr/local/share/man would fit, or are you on windows?
Ouch. That hurt.
> On 25 July 2014 05:11, Sitaram Chamarty <sitaramc@gmail.com> wrote:
>> On 07/25/2014 03:45 AM, Sheldon Els wrote:
>>> Hi
>>>
>>> A small tool I wrote that is useful for some workflows. I thought it'd
>>> be worth sharing. https://github.com/sheldon/git-feature-branch/
>>
>> As far as I can tell it's just a shell script; does it really need
>> installation instructions, and if so can they not be more generic than
>> "brew install"? Speaking for myself I have NO clue what that is.
prev parent reply other threads:[~2014-07-25 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 22:15 git feature-branch Sheldon Els
2014-07-25 4:11 ` Sitaram Chamarty
2014-07-25 5:40 ` Sheldon Els
2014-07-25 6:09 ` Sitaram Chamarty [this message]
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=53D1F4A8.4050509@gmail.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=sheldon@easyfundraising.org.uk \
/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).