The shell syntax "export X=Y A=B" is not understood by all shells.
Split the non portable line into separate lines like this:
A=B
X=Y
export A X
Signed-off-by: Torsten Bögershausen
---
contrib/remote-helpers/test-hg-bidi.sh | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff
The shell syntax "export X=Y" is not understood by all shells.
Split the non portable line into separate lines like this:
X=Y
export X
Signed-off-by: Torsten Bögershausen
---
contrib/remote-helpers/test-hg-hg-git.sh | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/c
Thorsten Jolitz writes:
> BTW - would 'git config --global core.editor zile' or 'git config
> --global core.editor /usr/bin/zile' the right way to set it (both did
> not work)? I can start Zile simply with 'zile' on the command line.
What do you mean by "did not work"? Does the launching fail?
Jiang Xin writes:
> I don't know how many programmers had been bitten by runing `git clean -fdx`,
> but I bet there were some. I think safety should be put to the 1st place.
> It is because "clean.requireForce" defaults to true, all people trend to run
> 'git clean' with the '--force/-f' option.
Jiang Xin writes:
> Maybe we can do like this:
>
> 1. Set the default value of 'clean.requireForce' to false.
> 2. Show a error message and do nothing, if there is not 'clean.requireForce'
> setting, but the user called with a '--force' flag.
> ( like a transition for the change of push.d
Am 4/26/2013 10:19, schrieb Yann Dirson:
>> 2. git rebase -i master fails unless I've rebased my branch on top of
>> master. I always wished I could do the equivalent of 'git rebase -i
>> master..', but I can't. Can we give the A..B syntax a new meaning in
>> the context of rebase, namely $(git m
2013/4/26 Matthieu Moy
>
> Jiang Xin writes:
>
> > * run `git clean` in interactive sessions,
> > * not a dry run,
> > * and not quiet.
>
> Err, does this mean I'll have:
>
> $ git clean
> fatal: clean.requireForce defaults to true and neither -n nor -f given;
> refusing to clean
> $ git clea
Tay Ray Chuan writes:
Hi,
> Is the GIT_EDITOR or EDITOR environment variable set? They may be
> overriding the core.editor setting.
Actually, EDITOR is set to Zile, so that should not be the problem:
[tj@hostname ~]$ echo $EDITOR
/usr/bin/zile
[tj@hostname ~]$ echo $GIT_EDITOR
[tj@hostname ~]
Hi,
Is the GIT_EDITOR or EDITOR environment variable set? They may be
overriding the core.editor setting.
--
Cheers,
Ray Chuan
On Fri, Apr 26, 2013 at 3:39 PM, Thorsten Jolitz wrote:
>
> Hi List,
>
> after experiencing one crash to many, I'm back to Standard Emacs
> (instead of Emacsserver/Emac
Jiang Xin writes:
> * run `git clean` in interactive sessions,
> * not a dry run,
> * and not quiet.
Err, does this mean I'll have:
$ git clean
fatal: clean.requireForce defaults to true and neither -n nor -f given;
refusing to clean
$ git clean --force
Are you sure [y/n]?
An optional conf
>2. git rebase -i master fails unless I've rebased my branch on top of
>master. I always wished I could do the equivalent of 'git rebase -i
>master..', but I can't. Can we give the A..B syntax a new meaning in
>the context of rebase, namely $(git merge-base A B)?
If I understand well, you're re
When running `git clean`, it will be convenient and safe to show a
confirm dialog and only delete files and directories when confirmed.
The confirm dialog will popup when:
* run `git clean` in interactive sessions,
* not a dry run,
* and not quiet.
There may be existing scripts that call `git
Hi List,
after experiencing one crash to many, I'm back to Standard Emacs
(instead of Emacsserver/Emacsclient), thus using 'emacs' (instead of
emacsclient) as git core editor triggers reading my huge init file and
is way to slow.
I would like to use Zile (a small Emacs clone) instead, and altho
101 - 113 of 113 matches
Mail list logo