threads / discuss / 691

How stop tracking a file?

Subject: How stop tracking a file?

## tl;dr

4 messages between May 22, 2005 and Jun 4, 2005.

replies: 3people: 3as markdown or json

jeff millar· May 22, 2005, 16:48 UTC · lore

cg-rm does two things
   rm -f "$@"
   git-update-cache --remove -- "$@"

Does cg support a way to stop tracking a file without deleting it? The idea was to cg-init an entire directory (such as /etc/ or some existing software project) and then selectivly stop tracking files, such as *.o, selected binaries, ld.so.cache, etc. as they turned up.

thanks,

jeff

Junio C Hamano· May 22, 2005, 17:10 UTC · re: jeff millar · lore

Re: How stop tracking a file?

>>>>> "jm" == jeff millar <wa1hco@adelphia.net> writes:

    jm> cg-rm does two things
    jm>    rm -f "$@"
    jm>    git-update-cache --remove -- "$@"

I do not do Porcelain, but something along the following lines should work:

    for path
    do
        git-update-cache --force-remove "$path"
    done

jeff millar· May 22, 2005, 18:29 UTC · re: Junio C Hamano · lore

Re: How stop tracking a file?

Junio C Hamano wrote:

Show 12 quoted lines

>    jm> cg-rm does two things
>    jm>    rm -f "$@"
>    jm>    git-update-cache --remove -- "$@"
>
>I do not do Porcelain, but something along the following lines
>should work:
>
>    for path
>    do
>        git-update-cache --force-remove "$path"
>    done
>

Seems a bit more difficult... [jeff@Desk gsmc-1.1]$ git-update-cache --force-remove main.o [jeff@Desk gsmc-1.1]$ cg-diff

Index: main.o
===================================================================
Binary files a5d1a55e0818ab11b71fee01bcd9053c4ecc65a6/main.o 
(mode:100644) and /dev/null (tree:uncommitted) differ
[jeff@Desk gsmc-1.1]$ cg-commit
Refusing to make an empty commit - the tree was not modified
since the previous commit. If you really want to make the
commit, do: commit-tree `tree-id` -p `parent-id`
A picky porcelain problem?

Petr Baudis· Jun 4, 2005, 01:24 UTC · re: jeff millar · lore

Re: How stop tracking a file?

Dear diary, on Sun, May 22, 2005 at 08:29:25PM CEST, I got a letter where jeff millar <wa1hco@adelphia.net> told me that...

Show 26 quoted lines

> Junio C Hamano wrote:
> 
> >   jm> cg-rm does two things
> >   jm>    rm -f "$@"
> >   jm>    git-update-cache --remove -- "$@"
> >
> >I do not do Porcelain, but something along the following lines
> >should work:
> >
> >   for path
> >   do
> >       git-update-cache --force-remove "$path"
> >   done
> >
> Seems a bit more difficult...
> [jeff@Desk gsmc-1.1]$ git-update-cache --force-remove main.o
> [jeff@Desk gsmc-1.1]$ cg-diff
> Index: main.o
> ===================================================================
> Binary files a5d1a55e0818ab11b71fee01bcd9053c4ecc65a6/main.o 
> (mode:100644) and /dev/null (tree:uncommitted) differ
> [jeff@Desk gsmc-1.1]$ cg-commit
> Refusing to make an empty commit - the tree was not modified
> since the previous commit. If you really want to make the
> commit, do: commit-tree `tree-id` -p `parent-id`
> A picky porcelain problem?

Ok, it took some non-trivial changes to cg-commit (this part was a quick hack before, now it looks a lot better), but cg-rm -n should now do what you want.

Thanks for the suggestion,

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor