> From: Alcolo Alcolo
> Because C can be a base commit of branches and merges, then it's a
> nightmare to rebase.
>
> I know that scripts exists to rebase merges (based on git-rev-list,
> git-cat-file, git-hash-object/git-commit-tree), but those scripts redo the
> git-filter-branch job.
Actu
> From: Trivender Ghangas
>
> I am trying to create an alias to simplify the process of cloning a
> repository with branches. I added alias in C:\Program
> Files\Git\etc\gitconfig
>
> gitconfig : https://www.dropbox.com/s/iumnqmkfk1ua8ty/gitconfig?dl=0
>
> I am getting error [attached error.
> From: Jon Zeolla
> Nevermind I guess the sticky bit trickles down throughout the whole
> directory structure.
Strictly speaking, the default value of the sticky bit when a
directory is created is the sticky bit value of its parent directory.
It trickles down when the directories are cre
> From: guru prasad
> Now my question is if the project version is 1.2.3.4
Git doesn't record "version numbers" of any sort. So you have to
store the version number(s) in one or more files, so that the program
that creates the archive file can extract the version number(s) and to
the correct th
> From: Sam Roberts
> Alternatively, there must be a command that gives the path to the root
> of the current .git tree, what is that command? I could use its output
> as an argument to git ls-files...
"git rev-parse --show-toplevel"
There are several related options; see the manual page.
Dale
> From: Vasily Makarov
>
> Git documentation defines commit ancestry as "reachability" of one commit
> from another.
> Formally, this might mean that every commit is ancestor and descendant of
> itself.
> I've also checked git merge-base --is-ancestor and found it returns "true"
> for same co
> From: citm09
> Currently my repo contains all these _notes folder located under different
> folders in this tree structure. How do I remove these _notes folder and
> it's contains. I do not want Git to track these _notes folders and it's
> contents.
What you need to do is put "_notes" in th
> From: Vasily Makarov
>
> It's not clear what the actual problem is.
> Git doesn't allow you to revert a commit you don't like?
> Or, maybe, you want to revert the merge commit?
Also, what does "revert" mean?
The "head of a branch" is simply a pointer (whose name is the branch
name) that point
> From: Thanakorn Sathitwitayakul
>
> I just install git-1.9.4-preview20140929 on my notebook pc, window 7 64 bit
> system. When I run git for the first time I got error message;
>
> sh.exe: /dev/null No such file or directory
>
> When I input some command in git, it run not thing but
>
> fa
> From: Guilherme
>
> The problem here is not the LF to CRLF conversion i know where that
> comes from. The problem is that doing
>
> git add '' CDD/CDD_Diag.c
>
> results in a message about another file which was clearly not my
> intention to add.
When I experiment, "git add ''" seems to have
> From: Dmitry Moscow
> I got to branch A which I want to 'merge' (preserving the differencies)
> with branch B.
> I run git read-tree -m HEAD
> I get a number of files updated and added in my working folder. Files that
> were absent in branch A are added, the differenceis are applied. But
>
> From: Arnaud BONNET
>Process used:
>1- Creation of deposit (made with the user "ace")
> 1- cd /home/ace/RDS/010
> 2 git init --separate-git-dir=/home/ace/RDS/010.git
> 3 echo "*%" >> /home/ace/RDS/010.git/.gitignore
> 4 echo "* ~" >> /home/ace/RDS/010.git/.gitignore
> From: krishna chaitanya kurnala
> I observed that in some cases, Git clone is not working, It either Hangs or
> it will take hours to clone some repos
>
> remote: Compressing objects: 100% (69/69), done.
> fatal: Out of memory, malloc failed (tried to allocate 2305676104 bytes)
> fatal: unpac
> From: John McKown
> commit -m 'myfile as of '
The manual page for git-commit says:
--date=
Override the author date used in the commit.
DATE FORMATS
The GIT_AUTHOR_DATE, GIT_COMMITTER_DATE environment variables and the
--date option support the following d
(I am using git version 1.8.3.1.)
Some references for git-fsck are like this:
https://git.help.collab.net/entries/22580428-Recovering-from-repository-corruption
$ git fsck --full
broken link fromtree 2d9263c6d23595e7cb2a21e5ebbb53655278dff8
toblob 4b9458b37
> From: OC0915566
> My company is upgrading the laptops and so, they're selling the old ones.
> The problem is, we've been using the old laptops to access remote git repos
> and the employer would like to clean all possible traces of repo URLs that
> have been accessed in these laptops. How do
Is the server process running on cmtoldshrdjk01? What do its log files
say? Can you connect to cmtoldshrdjk01 port 80 using telnet from the
server itself?
Dale
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this g
Guilherme writes:
> In my .git/info/exclude i have the patterns:
>
> !COM/config/Project.gny
> (...) other ignores
> /COM/config
> (...) more ignores
Is that perhaps a mistake? I believe you want the first line to be
"!/COM/config/Project.gny", because there is only one Project.gny file
that you
Thomas Ferris Nicolaisen writes:
> Here's what happens when I try removing some random object in my Git repo
> (using Git 2.0.0):
>
> git init; git add .;git commit -m "inital"
> rm .git/objects/00/79c7f07eb4bfbc08cc21f3324e7997e0b05415
> git fsck
>
> Checking object directories: 100% (256/256),
Jirong Hu writes:
> I have a GIT running on a Linux server. When I start the httpd service on
> the server, login with my id/password to
> http://cmtoldshrdjk01.dev.bmocm.com/web-app2.git/, my account got locked
> due to the following error found in the error.log
>
> Where shall I look for the
Jirong Hu writes:
> I just run another test. When I start the httpd, this message appears in
> the error.log. I have to shut it down immediately. I am wondering which
> product/process I am using will automatically send request to git? Maven,
> TeamCity, Artifactory? I am not running any builds
Fortunately, "git diff stash@{0}" will probably show the differences
between the stashed files and your current working directory. It seems
like Git is smart enough to know that the stash-pop is failing and not
delete record of the top stash.
But it does sound like there are a number of bugs in g
Kevin Wilson writes:
> Is there a command to roll back to the first commit in a repository?
Assuming that you want to reset the HEAD branch and the working
directory to be in the state of the first commit, the command would be:
git reset --hard {first-commit-hash}
As far as I know, there is
Konstantin Khomoutov writes:
> git log --reverse
>
> should help.
OK, that means that
git reset --hard $( git log --reverse --pretty=tformat:%H | head -1 )
will reset the HEAD branch, the index, and the working directory to the
"first" commit on the HEAD branch.
But you should first thi
Ramesh karanam writes:
>fatal: Unable to look up git.videolan.org (port 9418) (Name or service
> not known)
>
> Please suggest me about this issue
It is a networking problem of some sort, not a Git problem. You can
test with "telnet git.videolan.org 9418".
Dale
--
You received this mess
writes:
> I have a git repository, which master is empty and a branch contains
> android 5.0.0_r1. (Yes, I packed all android git repository into one).
>
> Now I want to push android 5.0.2_r1 into the repository. I checkout the
> master git an empty work place. Then create a new branch called
>
writes:
> I am pretty sure most of the files are the same by git diff.
Does that mean that you have actually done a git-diff and examined the
total size of the files whose content has changed?
> There is only small parts of the code base differ.
>
> Just like you said, I expect only sligh
writes:
>I did not use git diff because there are too many files.
>But when git add -A;git commit is don, most files are "added".
>This means git think most files are treated as new.
It means that git thinks most files are "new", in that git does not
believe that the file names exist
Rainer M Krug writes:
> Actually, I would like to exclude all files which have the
> following pattern:
>
> EnergyBalance.org[SOMETEXT]
>
> I tried
>
> EnergyBalance.org[.]
> EnergyBalance.org[*]
>
> but none worked.
I don't know what notation you're using for the "following pattern". Be
aware t
Rainer M Krug writes:
>> If you mean that the "base file name"
>> (the name within the nearest containing directory) matches the regexp
>> "EnergyBalance\.org.*", the "wildcard" version is "EnergyBalance.org*".
> Just one question: why do you escape the "."? As far as I understand, it
> has n
Vishal Dandge writes:
> i tried everyday to commit but was able to commit .
Do you mean "*un*able to commit?
What command did you execute? What error did you receive?
Dale
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscri
Owen Densmore writes:
> What's the best practice for "derived files" in a git repo?
Don't put them in the repository.
There are only two cases: (1) The version of the derived file in the
repo is correct relative the files that it's derived from. In that
case, the derived file is redundant. (2
John McWilliam writes:
> 1. I am a total beginner here and am constantly seeing referals to
> "~/FileName" This is obviously shorthand for something but what? Is it the
> location of the Git program directory or perhaps my working tree. How can I
> define this?
This is "shorthand" for the path
"Jagadeesh N. Malakannavar" writes:
> Is there any way to get branch details using tag name?
What do you mean? A tag denotes a particular commit, not a branch.
Dale
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from
phillip.l...@newcastle.ac.uk (Phillip Lord) writes:
> I have made a single branch clone of a repository. Originally, it was
> around 2Mb in size (compared to about 150Mb for a normal clone). Over
> time, though it has grown to around 20Mb.
>
> I've used a script that I found here...
>
> https://stu
This is so elegant, but:
Konstantin Khomoutov writes:
> $ git cat-file my-big-file^{} >/some/path/to/my-big-file
I think you have to say "git cat-file blob my-big-file^{} ...".
Dale
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
T
AJ Manoulian writes:
> I have a project in xcode and I did a time machine backup of everything
> before I did a clean install of the new OS. I had some changes in my
> project that I hadn't committed to git. When I brought all my files back on
> to the computer, all those changes seemed to be l
William Lasiewicz writes:
> I am looking in to it and the cherrypick command looks like what I am
> lookng for.
I'm no expert, but I think you can make that work.
> Developers will check in to the staging branch and we we are satisfied with
> the changes, we want to merge those checkin to rel
William Lasiewicz writes:
> All I want to do it create a repository on the server, add some files
> locally from my machine, push and go to another machine and actually see
> those files.
> In any other tool, this is completly easy
The Git command structure has grown over time and at no poin
Raluca Popa writes:
> For instance I want to create an archive (zip/jar - I am coding in Java)
> with the files I changed in order to send them via e-mail to a technical
> team lead. That team lead will download the archive I sent and create using
> a command line/user interface command, just t
acppcoder writes:
> Is there a way to make git diff show it's output in a format that can be
> traversed by 'jump to next error' in an editor such as emacs.
I'm not sure what you want. If you put the output of git diff into an
Emacs buffer, and put the buffer into diff-mode, Emacs probably has
Frank Gutierrez writes:
> *refs/heads files do _not_ point to objects*
>
> path: objects/78/803b535
The way to "find an object" in general is to use the "git cat-file"
command. You can give it the full 40-char hash of the object or the
ref/head name.
Dale
--
You received this message because
SoaringEagle writes:
> 1. # in the top-level directory of the cloned foo.git, add the bar repo
> as remote_bar:
> git remote add bar_remote
> git fetch bar_remote
>
> 2. # merge the bar repo into foo
> git merge -s ours --no-commit bar_remote/master
I'm no expert, but my guess i
python.beggine...@gmail.com writes:
> I am getting the following error while executing the below code snippet
> exactly at the line if uID in repo.git.log():, the problem is in
> repo.git.log(),the error happens way down in the bowels of the
> repo.git.log() command, I think because the output p
Yvon Fanfe writes:
> tried *"git clone https://path.to.the.server/project_directory/.git to
> clone the project but id doesn't worked. It always fail printing the
> error, *$ git clone path.to.the.server/project_directory/.git Cloning
> into 'xxx'... fatal: repository
> 'path.to.the.server/projec
Peng Yu writes:
> Hi, git-annex has a set of COMMON OPTIONS options (they are applicable
> to all git-annex commands). Is there something similar for git?
>
> https://git-annex.branchable.com/git-annex/
The 'git' manual page on my system includes this section, which appears
to be the common optio
Michael writes:
> Lets say you've got files set up to commit to one point in the tree,
> but you're actually in a different location. How do you move where you
> are / where a commit will go, without altering the files?
git reset --soft
looks like the command that does what you want.
Dale
--
Michael writes:
> keybounceMBP:config michael$ git commit -m "First test"
> [animalAging 0653a0b] First test
> 1 file changed, 140 insertions(+)
> create mode 100644 HarderWildlife.cfg
> keybounceMBP:config michael$ gitk --all
> ^C
> keybounceMBP:config michael$ git commit HarderWildlife.cfg -m
Michael writes:
>> those two sentences say the same thing. HEAD *is* "the branch tip pointer",
>> unless it's detached.
>
> Alright, maybe this is my first point of confusion.
>
> I thought "HEAD" is where you are at -- which of those letters you are
> pointing to.
> And, it may also be where a b
>From the original poster's point of view: Yes, you can use Git to store
various versions of MS Word documents, but you probably don't get much
benefit from doing so, since Git can't see into the different versions
of documents to see how they differ; to Git they're just blobs. OTOH,
it may be th
"Philip Oakley" writes:
> You may find that there are 'end of line' differences between the
> commits in the server, and the commits you have locally, which after
> eol conversion, look identical, but the different eol strings makes
> the sha1's different.
Yes, it's usually the case when files lo
John Bleichert writes:
> I understand that the underlying git principle is that "everything is
> local". Is there really no way to compare local to remote?
>
> Alternatively, should I be branching and merging every time I switch
> machines? This seems a strange way to use the tool.
>
> As I said
"Philip Oakley" writes:
> I think in this case the byte by byte check was identical,including line
> endings, which made it all the more awkward to sort out. (detecting file
> mode changes!)
Oh, that's interesting. Internally, it means that the recorded hash for
files matches between versions,
Konstantin Khomoutov writes:
>> My problem is, that I can not see possibility to checkout files from
>> another branch, based on a filelist from a text file.
>
> Once you have a text file with the list of file names,
> just do
>
> $ git checkout dev
> $ while read fname; do \
> git checko
Rainer M Krug writes:
> for some strange resold, git considers my emacs.org file (which is a text
> file) as a binary. This is only in one repository, and other .org files are
> seen as text.
http://fileinfo.com/extension/org says that .org is the extension used
by Lotus Organizer, so perhaps s
Chris Fillmore writes:
> I am imagining I putty into the server, checkout my branch, run the code.
> Is this possible? But what's to stop other team members from doing the
> same, at the same time? There are only three of us, we can communicate, but
> in principle I would prefer to have a bette
Suppose I've modified a file, or a set of files, and I want to return it
to the state in HEAD. I thought that "git checkout HEAD file1 file2
..." would do that, but git-checkout wants to preserve whatever changes
are present in the file tree. I'm sure that buried in Git's UI is a
command form tha
Theo G writes:
> We use Git on Windows and SourceTree as a Visual interface for Git.
It sounds like the only acceptable solution is one that can be operated
using SourceTree. So the question is, is there a facility in SourceTree
for this? I think you would be more likely to get a useful answer
Konstantin Khomoutov writes:
>>4. We would like to now be able to completely eject/remove the
>> commit/patch from the staging git repository, as if it never went in,
>> as well as any other commits that might be related to it that came in
>> after that, and NOT just attempt to reverse it by
Konstantin Khomoutov writes:
> I'd say there are only one reason for the
>
> git checkout HEAD file1 file2 ...
>
> invocation to fail file1 starts with a dash or double dash and gets
> interpreted as a command-line option.
I went back and checked my command window transcripts, and the problem
i
Ben Page writes:
>>git status
> On branch master
> Your branch is behind 'origin/master' by 2 commits, and can be
> fast-forwarded.
> (use "git pull" to update your local branch)
> Changes not staged for commit:
> (use "git add ..." to update what will be committed)
> (use "git checkout --
hiroki yasui writes:
> .gitconfig file is
> [alias]
> am = "!f(){ git commit -am \"$1\";};f"
First, there is no reason for your shell command to define a function
and then call it. The alias should just execute what is now the body of
the function:
> am = "!git commit -am \"$1\""
Seco
Eli writes:
> I'm trying to use Git over HTTP but I'm getting the error
> [Wed Apr 06 13:35:15.208592 2016] [cgi:error] [pid 6821] [client ...]
> AH01215: Not a git repository: '/var/git/repositories/my-project.git'
>
>
> On the client side I'm trying this:
>
> git clone http://myhost.com/git/my-
Kevin Wholley writes:
> I would like to see a history of any branch that merges into another
> branch. For example I have master as my production code. I also have a
> build branch and several development branches. When a development branch is
> ready to build we merge into our build branch. At
Ram Rachum writes:
> Then, as I said in the beginning, a friend pointed me towards the
> `--full-history` flag:
>
> $ git log --full-history --graph coffee
> * commit 0aa833916e908ea93902a6c4c227f9a884a1bcef
> |\ Merge: cf02fbb 3068c7d
Andrew Acevedo writes:
> I'm not familiar with git, but can the same tag be moved around on several
> branches and a history is kept which position on the branch it's been
> pinned too before?
I might be wrong, but I think the behavior (at least, the default
behavior) is to log the past values
Ram Rachum writes:
> $ git log --graph
> * commit b7a8d7aa001d06eb7491ab5fb447a8dd3aa421a8
> | Author: Ram Rachum
> | Date: Tue Apr 19 17:45:01 2016 +0300
> |
> | adding more to some-file
> |
> * commit 0aa833916e908ea93902a6c4c227f9a884a1bcef
> |\ Me
Ram Rachum writes:
> Administrator@Turing ~/Dropbox/Desktop/foo (development)
> $ git bisect start
>
> Administrator@Turing ~/Dropbox/Desktop/foo (development|BISECTING)
> $ git bisect good 3068
>
> Administrator@Turing ~/Dropbox/Desktop/foo (development|BISECTING)
> $ git bisect bad b7a8
> Bis
Ashley Coolman writes:
> Would make sense, no?
Unfortunately, no. The convention is that "--" is used to start long
options, which may have an optional value which is started with "=":
--[a-zA-Z0-0]+(=.*)?
Options that start with "-" use the long-established conventions for
single-letter o
Alekhya Vellanki writes:
> I'd like to start contributing to git.
>
> I have absolutely no idea about open source projects contributions.
> I am also pretty unclear about what bugs,patches etc are.
> When I tried reading source codes of a few project ideas for GSoc 2016, I
> could hardly understa
Konstantin Khomoutov writes:
> On Fri, 6 May 2016 18:56:01 +0300
> Kevin Wilson wrote:
>
>> Suppose you have a patch named 0001-great_change.patch
>>
>> Is there a way by which, using some git command, you can find out
>> which files this patch changes, without that
>> you will edit (or cat/more
Melvin Carvalho writes:
> In npm when you have an author there's a really nice feature ... namely you
> can add a URL :
>
> Author: Joe Bloggs (URL)
>
> In git you have the same message but without the optional URL at the end
>
> I was wondering how difficult it might be to add such a feature
Konstantin Khomoutov writes:
> Note that accessing commits by date is imprecise by its nature and,
> while useful sometimes, might indicate you're trying to do something
> wrong way.
In particular, the effects of time-zones can cause revisions to not have
the dates you expect them to. If you are
Sharan Basappa writes:
> Git mentions that state of the file as untracked, unmodified, modified and
> staged.
>
> As I understand untracked files are not yet in the respository.
> unmodified and modified is understood but what action results in a file
> being in staged state?
> is it git add or
Jeremy Yang writes:
> When I executed the "git clone git://url -b branch" cmd by multi-thread(40
> threads) at the same time,several cloned failures would often occur.
>
> However,the max-connections is setted to zero which is for no limit.
>
>
> *Git-daemon CMD:*
>
> /usr/bin/git daemon --verbo
Sharan Basappa writes:
> I am pretty much new to Git though I am using it for a couple of projects
> (without much understanding as such).
>
> In Git documents, it is mentioned that Git stores data as a stream of
> snapshots. Compared to other VCS tools, the only difference I am able
> to tell is
"Philip Oakley" writes:
> +1 for the nice explanation.
Thanks!
> The Index is also commonly called the *staging area* when viewed from an
> outward facing perspective (i.e. what do users do), with index being more
> commonly used for an inward facing perspective (e.g. for code development).
Sandor Hadas writes:
> However, if the very same script is added to cron then what happens:
> 1. Cron starts the script
> 2. Script invokes git clone
> 3. git clone spawns several "git-remote-https" processes
> 4. git returns while the spawned processes run
> 5. Commands based on the repo fail (if
Fabian Jonsson writes:
> I had a problem recently trying to add .dll files to git. No suggestion I
> found on SO seemed to help. When trying to add each file manually in the
> Git bash, I received a message saying that one of my ignore files prevented
> the file from being added. I would've lik
Konstantin Khomoutov writes:
> If you're pushing your project directly from Eclipse (I mean, by
> clicking some button or activating an entry of some pop-up menu) then
> you are not using Git but rather EGit -- an Eclipse's library to work
> with Git repositories which itself uses JGit -- a from-s
Sharan Basappa writes:
> Is there a way to retrieve the previous version of the file (that is, F.1).
It looks like "git fsck --unreachable" would output the hash of such a
file. Then you can use "git cat-file" to get the contents of each
object. You'll have to inspect the contents manually; as
Michael writes:
> Lets say I've got a topic branch. I've made a bunch of commits. It's
> messy. But it's done.
> What do I do with the leftover? I thought I could tag it as "closed",
> but I can't use the same tag more than once. What's the best way to
> mark it as done, or should I just delete t
Jerome Fouletier writes:
> I have one branch BR1 which receives frequent merges from branch BR0.
> Branch BR1 is tagged once per sprint, and I need to list the commits that
> have been made or merged since the last tag:
>
>
>-A1---B1(TAG)--C1---D1---E1---F1---G1(BR1)
>
>/
GUGLHUPF writes:
> 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 (several
> days(
contents aren't in ASCII, so you have to use "git cat-file -p
92f8f718eb9b19f921f20283e55c56e8dc66ed10" to read its contents:
tree d5d1ad293f8fdd4a4a4e0e9a73c5c3c851126c22
parent 39c83b086e141bb00d32737a4e2aae675d795f44
author Dale R. Worley 1470669963 -0400
committe
Sharan Basappa writes:
> The other question is, when it is time for Git to pick up the file
> associated with 100644 blob 0215040f90f133f999bac86eede7565c6d09b93d then
> it starts
> computing checksum of all the objects?
The point is that it doesn't have to *search* for the contents of the
fil
rh kramer writes:
> I've tried a number of variations, but I'm not getting the software (I
> guess git would call it the working tree) back. Some of the variations
> (all run from within sciscint_git):
>
> git checkout HEAD
> git checkout MASTER
> git checkout 76641b5
>
> I've also tried those
I am just beginning to use git. I've read the O'Reilly book (by
Loeliger and McCullough), and (unexpectedly) it didn't give me a clear
view of some of the messier aspects of git. So as a first question,
I'd like to know if anyone knows of an exposition that gives a clear
and accurate description
> From: Ryan Hodson
>
> If you're not looking for a submodule, you can just move the tracked files
> into a subdirectory with 'mv' or through your file browser. Then run 'git
> add .' in the project root and Git will figure out the file renames on its
> own. The 'git mv' command can be used to th
> From: "Philip Oakley"
>
> But is there some way to have git keep the repository files
> encrypted.
In practice, it seems the easiest way to do that is to put the
repository files in a separate, encrypted file system. That would
take tremendously less work than incorporating encryption in ever
> From: "Philip Oakley"
>
> > OK, so it seems that when you move files around, and then tell git to
> > notice that, git will automagically figure out what the moves were.
> > The O'Reilly book wasn't clear on that. (Nor did it explain how git
> > can distinguish a move from file that just happe
> From: "Philip Oakley"
>
> > Another question is this: I believe that the complete repository and
> > its status lives in the .git directory. So if I move ./.git to
> > ../.git,
> > it has the same effect as if I moved all the normal files into a
> > subdirectory of ".". Is that correct?
>
> From: "Philip Oakley"
>
> > How, then, do merges handle this information? If the "delta" is that
> > ./a/123 was moved into ./b/456, does the merging process understand
> > that, and move the same file in the destination directory? Or does it
> > only do so if ./a/123 in the destination direc
> From: Manlio Perillo
>
> [Git] "knows" that in your case they are the same: this is the
> reason why the push was fast; your home repo already have the objects
> with the same SHA.
>
> pull is slow because git has to unpack them; and yes, probably git could
> be a bit more smart and check if a
> From: Konstantin Khomoutov
>
> In general, it's impossible to copy a file from one branch to another,
> preserving its history.
It must be *possible* to do that: You could do a merge between the
head of A and the head of B, where all of the files of A are carried
into the merged version, and
> From: Konstantin Khomoutov
>
> Since Git only records snapshots of whole trees and does not really
> track individual files, there's no such *concept* as the history of an
> individual file -- it might appear to exist (thanks to the
> `git log ... ` command) but it's implemented as a filter
> a
> From: Konstantin Khomoutov
>
> > > Since Git only records snapshots of whole trees and does not really
> > > track individual files, there's no such *concept* as the history of an
> > > individual file -- it might appear to exist (thanks to the
> > > `git log ... ` command) but it's implemented
> From: lalebarde
>
> I am building a new SaaS product and a new company for it. This product
> will add some functionalities to Git via hooks. So I don't modify Git nor
> redistribute it. My service will be accessible by configuring the Git
> config file.
>
> Can I advertise my product with
> From: Konstantin Khomoutov
>
> > That's great! ... But the existence of git-blame means that git can,
> > *in practice*, trace the history of an individual file, and even
> > individual lines within a file.
>
> True, but your choice of the word "trace" is actually very precise, and
> that's wh
> From: Eric B
>
> [eric git]$ git clone https://e...@git.assembla.com/myproj.git
> Cloning into 'myproj'...
> Password for 'https://e...@git.assembla.com':
> error: RPC failed; result=22, HTTP code = 401
> fatal: The remote end hung up unexpectedly
>
> In all fairness, I do not know if that is
101 - 200 of 342 matches
Mail list logo
