On Mon, May 14, 2018 at 04:52:53PM +0200, Duy Nguyen wrote:
> On Sun, May 13, 2018 at 11:02 PM, Kevin Daudt wrote:
> > One data point indicating this is giving issues is that today on IRC a
> > user was confused why `git checkout pt` did not show any message and did
> > not
On Sun, May 13, 2018 at 11:02 PM, Kevin Daudt wrote:
> One data point indicating this is giving issues is that today on IRC a
> user was confused why `git checkout pt` did not show any message and did
> not checkout a remote branch called 'pt' as they expected. It turned out
>
Duy Nguyen writes:
>
> I would like an option to revert back to current behavior. I'm not a
> new user. I know what I'm doing. Please don't make me type more.
I can guarantee that nobody will stay a newbie. They either become
more proficient and aware of what they are doing
From: "Dannier Castro L"
On 13/05/2018 00:03, Duy Nguyen wrote:
On Sun, May 13, 2018 at 4:23 AM, Dannier Castro L
wrote:
For GIT new users, this complicated versatility of could
be very confused, also considering that actually the flag '--' is
On Sat, May 12, 2018 at 08:23:32PM -0600, Dannier Castro L wrote:
> Currently, is a complex command able to handle both
> branches and files without any distintion other than their names,
> taking into account that depending on the type (branch or file),
> the functionality is completely
> On 13/05/2018 00:03, Duy Nguyen wrote:
>
> > On Sun, May 13, 2018 at 4:23 AM, Dannier Castro L
> > wrote:
> >> For GIT new users, this complicated versatility of could
> >> be very confused, also considering that actually the flag '--' is
> >> completely useless (added
On 13/05/2018 00:03, Duy Nguyen wrote:
On Sun, May 13, 2018 at 4:23 AM, Dannier Castro L wrote:
For GIT new users, this complicated versatility of could
be very confused, also considering that actually the flag '--' is
completely useless (added or not, there is not any
"Dannier Castro L" wrote:
> Currently, is a complex command able to handle both
> branches and files without any distintion other than their names,
> taking into account that depending on the type (branch or file),
> the functionality is completely different, the easier
On Sun, May 13, 2018 at 4:23 AM, Dannier Castro L wrote:
> Currently, is a complex command able to handle both
> branches and files without any distintion other than their names,
> taking into account that depending on the type (branch or file),
> the functionality is
Currently, is a complex command able to handle both
branches and files without any distintion other than their names,
taking into account that depending on the type (branch or file),
the functionality is completely different, the easier example:
$ git checkout # Switch from current branch to .
10 matches
Mail list logo