From: Sitaram Chamarty <sitaramc@gmail.com>
To: Jim Vahl <jv@wmdb.com>
Cc: Drew Northup <drew.northup@maine.edu>,
Skot Davis <skotd122@gmail.com>,
git@vger.kernel.org
Subject: Re: A basic question
Date: Fri, 12 Oct 2012 06:28:49 +0530 [thread overview]
Message-ID: <CAMK1S_iMxju7Q7WSExw2nXqP0KqOEXFaYTMsmicYHMu6RAT-wA@mail.gmail.com> (raw)
In-Reply-To: <002801cda7d7$4792c260$d6b84720$@com>
On Thu, Oct 11, 2012 at 11:08 PM, Jim Vahl <jv@wmdb.com> wrote:
> Drew,
>
> Thanks for responding to my email!
>
> Yes, I did read most of the Book, although I admit that I skimmed over some
> of the more technical parts. There is still a key part of how git is used
> in a commercial environment which I don't understand.
>
> When we release a new version of our product, it is comprised of over a
> hundred files. Some of these files have not changed for years, and some
> have been revised/fixed/updated quite recently. But what is key is that all
> of these components have passed a review and testing process. A very
> important piece of information is what revision of each file made it into
> the release.
I'm afraid I don't have anything to add to what was already said but I
can't resist asking: are you coming from clearcase?
next prev parent reply other threads:[~2012-10-12 1:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 18:03 A basic question Jim Vahl
2012-10-10 19:36 ` Drew Northup
2012-10-11 17:38 ` Jim Vahl
2012-10-11 18:40 ` James Nylen
2012-10-11 18:51 ` Enrico Weigelt
2012-10-12 0:58 ` Sitaram Chamarty [this message]
2012-10-12 1:08 ` PJ Weisberg
[not found] ` <CA++fsGFruWFauX3XkynwcRLqK9H16frW86of3Y3ScgzGFmz=dg@mail.gmail.com>
2012-10-11 18:46 ` Dov Grobgeld
2012-10-12 15:56 ` A basic question - Thanks to all responders Jim Vahl
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=CAMK1S_iMxju7Q7WSExw2nXqP0KqOEXFaYTMsmicYHMu6RAT-wA@mail.gmail.com \
--to=sitaramc@gmail.com \
--cc=drew.northup@maine.edu \
--cc=git@vger.kernel.org \
--cc=jv@wmdb.com \
--cc=skotd122@gmail.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).