[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [egit-dev] locking mechanism
|
On Thu, Dec 19, 2013 at 10:26 AM, Laurent Goubet <laurent.goubet@xxxxxxx> wrote:
> I create a new file? I need to use Team > Add in order to stage its
> addition. This is the same behavior as the command line. (touch file1.txt ,
> then git add file1.txt)
> I change a file? I need to use Team > Add in order to stage the change. This
> is the same behavior ... (vi file1.txt ... changes... save... git add
> file1.txt)
> I fix a conflict in a file during a rebase? I need to use Team > Add... same
> behavior as command line.
>
> I delete file? Well this time the Team > Add has been done magically. This
> is not the same behavior as the command line. (rm file1.txt, git rm
> file1.txt)
+1 . I also don't like that we handle deletions so much different than
other modifications. (To be honest, I didn't even know we where
doing). I would vote for staging deletions explicitly.
