I have setup a subtree repo, with several subtrees that push to external
repositories.
In the subtree checkout directory within my main project, I have made
changes, and then I commit them using git add a few times and then git
commit; but only on items that are in that particular
Hi
"It's complicated"..
The devs do tend to consider which messages go to which file descriptor,
however there is a lot of "careful" discussion about backward compatibilities
and expectations and conflicts (between messages sharing fd's) that make it a
bit of a lottery.
It can also be an
On Mon, 1 Aug 2016, Xen wrote:
extundelete /dev/sdaX --restory-directory home//
That must be "restore-directory" of course.
cd /tmp
extundelete --restore-directory home//
cd RECOVERED_FILES
grep -r "text to search"
Would in general be all you need to do on a system you boot off USB or
On Fri, 29 Jul 2016, GUGLHUPF wrote:
Hi,
fairly new to git. Today I did a "git add somefile" and then decided I
wanted to unstage it. I did then a "git rm -f somefile". There was no git
command in between. Particularly no commit.
git wiped the file from disk. I worked very hard on that file
Hi, I'm studying git for own project and I wonder why git shows some
messages using stderr. For example, if you checkout from a to master git
shows '(1) switched to branch master, (2) Your branch is up-to-date with
"origin/master".' I have found (1) is through stderr and (2) is stdout.
Another