(master)]$
Any idea what configuration got change over night ? I have no idea how to fix
it? Please help me.
Regards,
Arup Rakshit
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.
use "git add" to track)
It did not work. Then using `git commit -h` told me, *-a* will work, for
*tracked files*. Is there any way to add untracked files in stage, and commit
in
a single line ?
--
===
Regards,
Arup Rakshit
--
To unsubscribe from this list: send the l
Hi,
Is there any difference between the below 2 commands ? I didn't see anything.
git rm --cached -- ..
git checkout -- ..
--
===
Regards,
Arup Rakshit
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@
ad of this mailing list. I
actually wanted to ask the below
git rm -- cached -- ..
git reset HEAD ..
--
=======
Regards,
Arup Rakshit
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info
On Monday, May 19, 2014 12:01:07 PM you wrote:
> On Mon, May 19, 2014 at 09:12:47PM +0630, Arup Rakshit wrote:
> > Is there any difference between the below 2 commands ? I didn't see
> > anything.
> >
>
> Does that help?
For me who is in Git just 6-7 days
ac:arup_git shreyas$ ls
git_1.txt
Arup-iMac:arup_git shreyas$
--
===
Regards,
Arup Rakshit
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tuesday, May 20, 2014 11:56:57 AM you wrote:
> On 5/20/2014 10:38 AM, Arup Rakshit wrote:
> > I was following some tutorial (http://gitref.org/branching/#merge) - and
> > doing it in my console :
>
> Because you never committed the original file to the master branch
>
; controlled file,
This is still didn't get it. If an untracked file didn't come in the new
branch, how would I able to add it to stage ? I am not getting this part. You
are right, but I am not able to understand this one, my bad! :(
--
===
Regards,
Arup Rakshit
--
To uns
On Tuesday, May 20, 2014 11:24:11 AM you wrote:
> Arup Rakshit writes:
>
> Untracked files and modifications to files in your working directory
> do not belong to your current branch. This is to allow you, after
> starting to work on one branch then realizing that the changes
want
this is, some times I have at least 30 files, whereas I want to _stage_ say, 20
files, not the rest 10. During _staging_ can I tell *git add* the same. I used
*git add -h*, which didn't show me any such hints about my need.
--
===
Regards,
Arup Rakshit
--
To unsubscribe
On Monday, May 26, 2014 10:23:22 PM you wrote:
> On di, 2014-05-27 at 00:33 +0630, Arup Rakshit wrote:
> > Now, you can see, I have staged all the files first using *git add
> > -A*, then _unstaging_ those I don't want to _stage_ right now. Now can
> > this be done, in t
e only way to
do it.
Thanks for your reply.
--
=======
Regards,
Arup Rakshit
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
the remote repo's *master* branch, how to restore it to its previous
stage using *git* ?
-
Regards,
Arup Rakshit
Debugging is twice as hard as writing the code in the first place. Therefore,
if you write the code as cleverly as possible, you are, by defin
ot read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
arup@linux-wzza:~/Ruby/yzz>
Can anyone tell me what is the problem ?
--
Regards,
Arup Rakshit
Debugging is twice as hard as writing the code in the
But I am looking for any differences -
a) git reset --soft and git reset --keep
b) git reset --hard and git reset --merge
--
Regards,
Arup Rakshit
Debugging is twice as hard as writing the code in the first place. Therefore,
if you write the code as cleverly
ow to upgrade then ?
--
Regards,
Arup Rakshit
Debugging is twice as hard as writing the code in the first place. Therefore,
if you write the code as cleverly as possible, you are, by definition, not
smart enough to debug it.
--Brian Kernighan
--
To unsubscribe
ell `git pull` also not to consider the change the
file, and skip it or something else ?
--
====
Regards,
Arup Rakshit
Debugging is twice as hard as writing the code in the first place. Therefore,
if you write the code as cleverly as possible, you are, by definition, not
On Friday, January 23, 2015 11:31:40 AM you wrote:
> Arup Rakshit writes:
>
> > I asked git not to track any changes to the file .gitignore. To do
> > so I did use the command - git update-index --assume-unchanged
> > .gitignore.
>
> You are not asking Git to do a
of advice in the last paragraph on that page is wrong (and
> it has been wrong from the day it was written).
>
> The gitignore(5) documentation used to have a similar incorrect
> piece of advice but we finally corrected it recently.
>
> Cf. http://thread.gmane.org/gmane.comp.ve
zenia (SJ002)]$
Why it is throwing error ? And how to achieve this without taking the help of
the file `.gitignore` ?
--
====
Regards,
Arup Rakshit
Debugging is twice as hard as writing the code in the first place. Therefore,
if you write the code as cleverly as p
On Sunday, March 15, 2015 01:30:04 PM you wrote:
> Hi,
>
> On 03/15, Arup Rakshit wrote:
> > Hi,
> >
> > I am trying to ignore 2 files, but getting error -
> >
> > [arup@sztukajedzenia (SJ002)]$ git status
> > # On branch SJ002
> > # Untrac
On Sunday, 15 March 2015 11:15 PM, Kevin D wrote:
On Sun, Mar 15, 2015 at 05:58:19PM +0100, t.gumme...@gmail.com wrote:
> On 03/15, Arup Rakshit wrote:
> > On Sunday, March 15, 2015 01:30:04 PM you wrote:
> > >
> > > With --assume-unchanged you're promising git
22 matches
Mail list logo
