init
$ mkdir D
$ echo "Hi" > D/F
$ git add D/F
$ rm -r D
$ echo "Hey" > F
$ git rm D/F
This works as expected, and the only difference is the name of the file of
the last echo.
Is this the expected behavior of git rm?
--
View this message in context: http://gi
On 04/03/2013 04:49 PM, jpinheiro wrote:
Hi all,
We are students from Universidade do Minho in Portugal, and we are using git
in project as a case study.
While experimenting with git we found an unexpected behavior with git rm.
Here is a trace of the unexpected behavior:
$ git init
$ mkdir D
$
Hello (again, psst, after a long time),
it happened yesterday that i needed to do
$ git diff HEAD:FILE COMMIT:SAME-FILE |
> (cd src && git apply -)
but found that didn't work with v2.0.0 (silently succeeds?, doing
nothing). It works without the subshell and the cd(
Steffen Nurpmeso venit, vidit, dixit 24.07.2014 15:29:
> Hello (again, psst, after a long time),
>
> it happened yesterday that i needed to do
>
> $ git diff HEAD:FILE COMMIT:SAME-FILE |
> > (cd src && git apply -)
>
> but found that didn't wor
Michael J Gruber writes:
> Steffen Nurpmeso venit, vidit, dixit 24.07.2014 15:29:
>> Hello (again, psst, after a long time),
>>
>> it happened yesterday that i needed to do
>>
>> $ git diff HEAD:FILE COMMIT:SAME-FILE |
>> > (cd src &&am
>
>>> $ git diff HEAD:FILE COMMIT:SAME-FILE |
>>> > (cd src && git apply -)
>>> ...
>>
>> Ah little more context would help. Are you diffing files in the subdir
>> src, or a file at the root which happens to be present in the subdir src
>> a
ppened yesterday that i needed to do
|>>>
|>>> $ git diff HEAD:FILE COMMIT:SAME-FILE |
|>>>> (cd src && git apply -)
|>>> ...
|>>
|>> Ah little more context would help. Are you diffing files in the subdir
|>> src, or a file
Change occurrences "cd" followed by "fetch" on a single line to be on
two lines.
This is purely a stylistic change pointed out in code review for an
unrelated patch. Change the these tests use so new tests added later
using the more common style don't look out of pl
Hi,
I frequently have the need to cd back to the root of the current git workdir
and created to alias for this:
git alias root = rev-parse --show-toplevel
shell alias cdgit = cd $(git root)
Maybe somebody likes this.
Now it would be cool, to have an alias to cd into a specific subdir of the
On Mon, Sep 16, 2013 at 09:01:14PM +0200, Thomas Koch wrote:
> Hi,
>
> I frequently have the need to cd back to the root of the current git workdir
> and created to alias for this:
>
> git alias root = rev-parse --show-toplevel
>
> shell alias cdgit = cd $(git root)
&
also sprach Thomas Koch [2013.09.16.2101 +0200]:
> shell alias cdgit = cd $(git root)
I've tried to make this happen many years ago, but I never finished
the ZLE widget that did it. The idea was to bind 'tab' to a function
that would replace an occurrence of ~g in $LBUFFER with
Many tests do something like:
(
mkdir foo &&
cd foo &&
git init
)
You can do the same these days with "git init foo", which
makes the tests shorter and simpler to read.
Signed-off-by: Jeff King
---
Unlike the last patch, this one _could_
omething else)
calls restore_env() multiple times, and restore_env frees orig_cwd such
that subsequent restore_env(0) with external_alias=0 tries to cd to a
random location.
I have no idea whether orig_cwd=0 after freeing or something else would
be the proper fix.
Michael
LANG=C git sss
WARNING: You
C)'
# function could fix that but it is not in Python until 3.3.
time_in_seconds() {
- python -c 'import time; print int(time.time())'
+ (cd / && python -c 'import time; print(int(time.time()))')
}
# Try to pick a unique port: guess a large numbe
hat area. Funny, though, that my user name shows up...
>
> I think the reason is that git.c's handle_alias() (or something else)
> calls restore_env() multiple times, and restore_env frees orig_cwd such
> that subsequent restore_env(0) with external_alias=0 tries to cd to a
> random loc
Signed-off-by: Thomas Braun
---
Today I found out that both %cd and %ad pretty print format
specifications honour the --date option as shown in:
$ git log --abbrev=8 --date=short --pretty="%h (%s, %cd)" -n1
5bdb1c4e (Merge pull request #245 from
kblees/kb/master/fix-libsvn-addres
PRETTY FORMATS' format: documentation says, "%ad: author date
(format respects --date= option)", and similarly for %cd.
But git-archive does not support the --date= option for changing the
date format in $Format:%ad$ or $Format:%cd$ substitution strings.
Relatedly, I want a shor
ttime(CLOCK_MONOTONIC)'
# function could fix that but it is not in Python until 3.3.
time_in_seconds() {
- python -c 'import time; print int(time.time())'
+ (cd "$TEST_DIRECTORY" && python -c 'import time;
print(int(time.time()))')
}
# Try to pic
Thomas Braun writes:
> Signed-off-by: Thomas Braun
> ---
>
> Today I found out that both %cd and %ad pretty print format
> specifications honour the --date option as shown in:
>
> $ git log --abbrev=8 --date=short --pretty="%h (%s, %cd)" -n1
> 5bdb1c4e (Merge
On Thu, Oct 09, 2014 at 11:19:36AM -0500, Derek Moore wrote:
> PRETTY FORMATS' format: documentation says, "%ad: author date
> (format respects --date= option)", and similarly for %cd.
>
> But git-archive does not support the --date= option for changing the
>
On Thu, Oct 09, 2014 at 03:24:28PM -0400, Jeff King wrote:
> On Thu, Oct 09, 2014 at 11:19:36AM -0500, Derek Moore wrote:
>
> > PRETTY FORMATS' format: documentation says, "%ad: author date
> > (format respects --date= option)", and similarly for %cd.
> >
> I don't see a big problem with that. But I wonder if we would do better
> to introduce arbitrary strftime-like formatting, so we do not have to
> keep adding new formats.
My thoughts exactly...
This list seems to be a prove-yourself-with-patches sorta place. If I
can find the time, I'll try att
-submodule-update.sh
@@ -288,10 +288,7 @@ test_expect_success 'submodule update --remote --recursive
--init should fetch m
git commit -m "add l1 module with branch b1 in super5" &&
git submodule init submodl1b1 &&
git clone super5 super &&
ificial Intelligence and Cognitive Science
(AICS '13)
1st International Conference on Innovative Computing and Information Processing
(INCIP '13)
For the accepted papers we provide
---
a) Book (Hard-Copy).
b) CD-ROM Proceedings with all collocated con
24 matches
Mail list logo
