On 2016-05-21 17:52-0500, David A. Greene wrote:
Mathias Nyman writes:
For recalling where a subtree came from; git-subtree operations 'add'
and 'pull', when called with the parameter add this to the
commit message:
git-subtree-repo:
I am sorry it tooks a couple
Mathias Nyman writes:
> For recalling where a subtree came from; git-subtree operations 'add'
> and 'pull', when called with the parameter add this to the
> commit message:
> git-subtree-repo:
I am sorry it tooks a couple of months to respond. I am finally coming
up
On 2016-02-26 14:49-0500, Eric Sunshine wrote:
On Fri, Feb 26, 2016 at 3:28 AM, Mathias Nyman wrote:
On 2016-02-25 17:23-0500, Eric Sunshine wrote:
On Tue, Feb 23, 2016 at 5:25 AM, Mathias Nyman
wrote:
- cat <<-EOF
- $commit_message
On Fri, Feb 26, 2016 at 3:28 AM, Mathias Nyman wrote:
> On 2016-02-25 17:23-0500, Eric Sunshine wrote:
>> On Tue, Feb 23, 2016 at 5:25 AM, Mathias Nyman
>> wrote:
>>> - cat <<-EOF
>>> - $commit_message
>>> -
>>> -
On 2016-02-25 17:23-0500, Eric Sunshine wrote:
On Tue, Feb 23, 2016 at 5:25 AM, Mathias Nyman wrote:
For recalling where a subtree came from; git-subtree operations 'add'
and 'pull', when called with the parameter add this to the
commit message:
git-subtree-repo:
On Tue, Feb 23, 2016 at 5:25 AM, Mathias Nyman wrote:
> For recalling where a subtree came from; git-subtree operations 'add'
> and 'pull', when called with the parameter add this to the
> commit message:
> git-subtree-repo:
>
> Other operations that don't have the
For recalling where a subtree came from; git-subtree operations 'add'
and 'pull', when called with the parameter add this to the
commit message:
git-subtree-repo:
Other operations that don't have the information, like
'merge' and 'add' without , are unchanged. Users with such a
workflow
7 matches
Mail list logo