git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Jon Loeliger <jdl@freescale.com>
Cc: git@vger.kernel.org
Subject: Re: My Embarrasingly Stupid Git question....(*)
Date: Wed, 31 Aug 2005 12:58:47 -0700	[thread overview]
Message-ID: <7vacixanew.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 1125506707.13577.29.camel@cashmere.sps.mot.com

Jon Loeliger <jdl@freescale.com> writes:

> (*) -- I knew I didn't need to bother the list with this
>     question.  And that as soon as I asked for external help,
>     the answer would become clear. Sorry to have bothered you.

That's OK.  As I stated before, the primary motivation that got
me involved in git was to help people who do Linux kernel, so
any question regarding the Linus kernel tree extracted from a
copy of his git repository is welcome here, at least to me.

I do not know Cogito very well.  I keep the latest Cogito source
around all the time so that I can figure things out whenever
need arises by reading it.  Most of the time, I would not
offhand know answers to questions like "what does cg-rm do and
what's the difference between it and 'cvs rm'".

Using the core GIT tools only, the sequence of what you did
would have been:

------------------------------------------------
$ git clone <url> <dir> && cd <dir>
$ git checkout -b jdl master
$ rm include/asm-ppc/sockios.h
$ rm include/asm-ppc/socket.h
$ rm include/asm-ppc64/sockios.h
$ rm include/asm-ppc64/socket.h
$ git add include/asm-powerpc/sockios.h
$ git add include/asm-powerpc/socket.h
$ git commit -a -s
------------------------------------------------

           reply	other threads:[~2005-08-31 19:58 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1125506707.13577.29.camel@cashmere.sps.mot.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vacixanew.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=jdl@freescale.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).