Thank you. I will try the vcsh.
On Thursday, 13 March 2014 15:14:01 UTC+8, Thomas Ferris Nicolaisen wrote:
>
> On Thursday, March 13, 2014 4:19:06 AM UTC+1, Tony George wrote:
>>
>> Hi,
>>
>> I have a bitbucket private repo for dotfiles. This contains files like
>> .vimrc and so on.
>> For Vim, I
- Original Message -
From: Alberto Fanjul Alonso
To: git-users@googlegroups.com
Sent: Sunday, March 16, 2014 10:38 AM
Subject: [git-users] respect --color option on format placeholders
I love to use git log from command line, exactly:
git log --color --graph --oneline --d
On Sun, 16 Mar 2014 09:29:24 -0700 (PDT)
Unsigned Zero wrote:
> Resolved my problems. I don't know of Google Group accepts markdown
[...]
No it doesn't. But the neat thing about wiki markups is that they're
perfectly readable without being rendered.
--
You received this message because you ar
Resolved my problems. I don't know of Google Group accepts markdown but
here is my solution.
Following
[this](https://stackoverflow.com/questions/13746554/git-send-email-is-not-a-git-command-see-git-help
"git: 'send-email' is not a git command. See 'git --help'") stackoverflow
post, git-email
While reading your explanation I've imagined Bart Simpson writing "Git
is always working on the whole index" over and over on the desk:)
Sorry.
On Sun, Mar 16, 2014 at 2:35 PM, Johannes Müller
wrote:
> Hi,
>
> I can answer the question to why I ended up using reset at least, though
> I can imag
I love to use git log from command line, exactly:
git log --color --graph --oneline --decorate
or for a first look
git log --color --graph --oneline --decorate --simplify-by-decoration --all
but sometimes I miss the date, committer email or the like, and using
format string does not apply colo
Hi,
I can answer the question to why I ended up using reset at least, though
I can imagine more scenarios. I wanted to do a reset on the current
working directory (read subdirectory of the repository) instead of on
the whole repository, and assumed git would do as I intuitively expected
it to, wit