On Wed, Jan 9, 2019 at 10:08 PM Johannes Schindelin
wrote:
> Having said that, it is an unintended regression in the built-in rebase.
> Markus, could you come up with a minimal test case, preferably in the form
> of a patch to t/t3415-rebase-autosquash.sh?
Something like this, perhaps? ("gmail co
> commit 6be4595edb8e5b616c6e8b9fbc78b0f831fa2a87
> Author: Jeff King
> Date: Tue Oct 3 09:46:06 2017 -0400
>
> color: make "always" the same as "auto" in config
>
> Would you like to take a stab at adding it? builtin/commit.c and
> Documentation/git-{commit,
On Tue, Oct 10, 2017 at 8:16 AM, Jonathan Nieder wrote:
> Hi,
>
> Nazri Ramliy wrote:
>
>> I used to work before, but now:
>>
>> $ git version
>> git version 2.15.0.rc0.39.g2f0e14e649
>>
>> $ git status --color=always
>> err
I used to work before, but now:
$ git version
git version 2.15.0.rc0.39.g2f0e14e649
$ git status --color=always
error: unknown option `color=always'
usage: git status [] [--] ...
Is it no longer supported?
nazri
On Thu, May 11, 2017 at 2:42 PM, Junio C Hamano wrote:
> I am not a heavy submodule user so what I think may not count, but I
> think the "upstream" changing the URL of the submodule should be a
> rare and notable event. Making it easy to automatically run "sync"
> without thinking would be a hug
Hi,
The command "git submodule update" accepts an "--init" flag to
initialize an uninitialized submodules.
Shouldn't it also accept "--sync" flag in order to sync and unsync'd submodule?
Otherwise it seems like I'll have to do "git submodule update" twice
in order to update an already initialize
On Sat, Sep 24, 2016 at 12:34 AM, Stefan Beller wrote:
> git -C path/to/sub --keep-prefix ls-files
Note that the above can also be written like so (and works
identically), due to the fact that -C can be given multiple times:
git -C path -C to -C sub --keep-prefix ls-files
nazri
On Tue, Oct 27, 2015 at 12:56 AM, Jens Lehmann wrote:
> Which seems a bit error prone as you could forget to update the submodules
> and build incorrect rpms from them, or am I missing something?
For my case I'm not building the rpms directly after merging in the fixes
done in the octopus branch,
On Mon, Oct 26, 2015 at 7:10 AM, John Smith wrote:
> When would people routinely check out a branch and want to stay with the
> submodules as
> the have been checked out for the old branch?
I do this a lot. At my $dayjob we have a super project with bunch of
sub projects.
Each subproject has its
Hi,
I noticed that the format of the comment lines in a rebase instruction
sheet has become stricter - it could no longer begin with spaces or
tabs. The comment char ("#" for example) has to appear on the first
column.
This break my little script (activated via some key binding in my
$EDITOR) for
really does help in deciding the
reorder and squash candidates.
The files list came from this:
git show --raw $sha1|awk '/^:/ {print " '"${comment_char}"'\t"$0}'
Thoughts?
nazri
From 4826875c14554d4fa5098ddf9499c33cb7b9001b Mon Sep 17 00:00:00 2001
Hi,
Sorry it took me a while to get back on this. Reroll at the bottom ...
On Tue, Sep 10, 2013 at 12:32 AM, Junio C Hamano wrote:
> Nazri Ramliy writes:
>
>> Subject: git: run in a directory given with -C option
>>
>> This is similar in spirit to to "mak
On Mon, Sep 09, 2013 at 01:01:33AM -0400, Eric Sunshine wrote:
> On Sun, Sep 8, 2013 at 9:49 PM, Nazri Ramliy wrote:
> Thanks for the reference. I did read that thread earlier. It doesn't
> really answer my question, but perhaps it's not terribly important
> since the intera
Sat, Apr 20, 2013 at 12:12 AM, Jeff King wrote:
> On Fri, Apr 19, 2013 at 08:21:48PM +0800, Nazri Ramliy wrote:
>> diff --git a/Documentation/git.txt b/Documentation/git.txt
>> index 6a875f2..20bba86 100644
>> --- a/Documentation/git.txt
>> +++ b/Documentation/git.txt
On Wed, Sep 04, 2013 at 02:36:47PM +0800, Nazri Ramliy wrote:
> On Wed, Sep 4, 2013 at 6:46 AM, Junio C Hamano wrote:
> > Does the above format correctly without the usual "second and
> > subsequent paragraphs are not indented, but has '+' in place of
> > a b
On Wed, Sep 4, 2013 at 6:46 AM, Junio C Hamano wrote:
> I do not care too deeply either way, but I am curious if there was a
> reason why you changed the earlier to ? Somehow,
> when we _know_ a path has to be a directory, I find it easier on the
> readers to spell that out, instead of saying "t
base); done
While doable the methods shown above are arguably more suitable for
scripting than quick command line invocations.
With this new option, the above can be done with fewer keystrokes:
1. git -C ~/foo status
2. git -C ../.. grep foo
3. for d in d1 d2 d3; do git -C $d svn rebase
On Sun, Sep 01, 2013 at 12:48:23AM -0400, Eric Sunshine wrote:
> On Fri, Aug 30, 2013 at 9:35 AM, Nazri Ramliy wrote:
>> With this new option, the above can be done with less keystrokes:
>
> Grammar: s/less/fewer/
>
> More below...
Thanks for taking the time to review this p
e --git-dir and --work-tree.
Signed-off-by: Nazri Ramliy
---
This is a reroll of [1]. The only difference is the rewording of the
commit message. I'm resending this as I've found it to be useful in my
daily git usage in that it helps me stay focused on what I'm doing in
the cu
On Mon, Aug 19, 2013 at 4:37 PM, Thomas Rast wrote:
> Hmm, IIUC that's actually not a bug or even a roughness; it's an
> artifact of how the :pattern:file syntax is defined. It takes the first
> _funcname line_ matching 'pattern', up to (but excluding) the next
> funcname line.
>
...
> Or is ther
On Sun, Aug 18, 2013 at 6:33 PM, Zhan Jianyu wrote:
> Such a requirement came into my mind when I am tracking a gloomy C
> struct , with lengthy list of elements which are either elaborated or
> opaque. So I use git blame to track it down and found that its
> original version is quite simple and
Hi,
>From "git help grep":
--no-index
Search files in the current directory that is not managed by Git.
--untracked
In addition to searching in the tracked files in the working tree,
search also in untracked files.
>From the description above I woul
tersely:
$ git -C ~/foo status
A new test script is added to verify the behavior of this option with
other path-related options like --git-dir and --work-tree.
Signed-off-by: Nazri Ramliy
---
Jeff: Thanks for pointing out the mistakes.
But I did not address your concern:
> I know you
This is similar in spirit to to "make -C dir ..." and "tar -C dir ...".
Signed-off-by: Nazri Ramliy
---
Often I find myself needing to find out quickly the status of a repository that
is not in my currenct working directory, like this:
$ (cd ~/foo; git log -1)
W
On Thu, Oct 4, 2012 at 5:01 PM, Ævar Arnfjörð Bjarmason
wrote:
> $ time (echo | ~/g/git/git-upload-pack . | pv >/dev/null)
Totally off-topic, but ...
Thanks for making me look up what pv is. I remember checking it out
quiet sometime
ago and have forgotten about it altogether.
Now I can
On Tue, Sep 4, 2012 at 7:25 PM, Коньков Евгений wrote:
> sot this allow:
> git diff 1 same asgit diff a1.txt
> git diff 2 same asgit diff a2.txt
>
> git add 1same asgit add a1.txt
> in case there are may be files with such names I may appply option -s,fo
26 matches
Mail list logo
