Julius Musseau writes:
> I'm embarrassed to realise your approach matches the top-voted
> stack-overflow answer on the subject:
> https://stackoverflow.com/a/5201642
I personally do not visit stack-overflow, but I am happy to see that
there are people who remember "right"
On Thu, Feb 22, 2018 at 10:04 PM, Junio C Hamano wrote:
> Julius Musseau writes:
>
>> git squash []
>>
>> Squashes ..HEAD into a single commit. Replaces HEAD with the
>> result. If not specified, defaults to the current branch's
>> upstream (a.k.a.
Julius Musseau writes:
> git squash []
>
> Squashes ..HEAD into a single commit. Replaces HEAD with the
> result. If not specified, defaults to the current branch's
> upstream (a.k.a. @{upstream}).
>
> Rationale:
>
> This command provides an intuitive mechanism for
Hi, Git Developers,
Thanks for your help regarding my earlier email (trying to break git
pull --rebase).
I just wanted to warn you all that my first attempt at a patch is
imminent. I'm working on a "git squash" command. Here's a quick
summary:
--
git squash []
Squashes ..HEAD into a
4 matches
Mail list logo