On Sat, Feb 4, 2017 at 7:16 PM, Philip Oakley wrote:
> From: "Duy Nguyen"
>>
>> On Sat, Feb 4, 2017 at 3:28 AM, Jacob Keller
>> wrote:
>>>
>>> +
>>> +$ git reset HEAD^ <1>
>>
>>
>> It may be a good idea to add -N here, so that 'add -p' can pick up the
>> new
From: "Duy Nguyen"
On Sat, Feb 4, 2017 at 3:28 AM, Jacob Keller
wrote:
+
+$ git reset HEAD^ <1>
It may be a good idea to add -N here, so that 'add -p' can pick up the
new files if they are added in HEAD.
When looking at the man page for `reset` [1] it
On Sat, Feb 4, 2017 at 3:28 AM, Jacob Keller wrote:
> +
> +$ git reset HEAD^ <1>
It may be a good idea to add -N here, so that 'add -p' can pick up the
new files if they are added in HEAD.
> +$ git add -p<2>
--
Duy
Jacob Keller writes:
> +Split a commit into two::
Let's say "...into two (or more)" to match what appears in
"SPLITTING COMMITS" section of "rebase -i" documentation. Yours is
written as a sequence of more concrete steps than the existing one
over there, so it may also make sense to add referen
From: Jacob Keller
It is often useful to break a commit into multiple parts that are more
logical separations. This can be tricky to learn how to do without the
brute-force method if re-writing code or commit messages from scratch.
Add a section to the git-reset documentation which shows an exam
5 matches
Mail list logo