hi guys,
I have repo A and repo B which is a subset of A by extracting folder
related commits and creating a new repo out of it.
since it was done with filter-branch there are new SHA1's and files paths
had changed to some extent as well.
my question is - if I would like to keep syncing repo B
Hi Gabby,
If you are looking at a single directory / sub-tree of the main repo, then
maybe have a look at the "Sub-tree merge" capability. I have not used it
myself, but it sounds like it matches your use case.
[The main Git project uses it for merging in the git-gui and gitk repositories].
P
thanks Philip.
if I need to update a sub folder (not a sub tree), how can I use the sub
tree merge ?
I have the sub folder in repo A and would like to apply the commits for
this folder on repo B, which file paths had changed there along with
sha-1's since I had to filter-branch repo B to create it
Like I said, I've not used it, but a little googling (`working with git
subtree`) got
https://www.atlassian.com/blog/git/alternatives-to-git-submodule-git-subtree or
https://medium.com/@porteneuve/mastering-git-subtrees-943d29a798ec
which looks like it might be a reasonable discussion.
It maybe
Hi, Is there an option or version of GIT with a database that keeps the
last file stamp of committed files??
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an e
On Mon, Jun 5, 2017 at 3:31 PM wrote:
> Hi, Is there an option or version of GIT with a database that keeps the
> last file stamp of committed files??
>
>
It depends what you mean by "file stamp".
If "file stamp" means a cryptographically strong checksum of the contents
of the file, then yes, t
In general, No. It's contrary to the basic Git VCS view. it's the content that
matters not some 'irrelevant' metadata.
https://confluence.atlassian.com/bbkb/preserving-file-timestamps-with-git-and-mercurial-781386524.html
There's a rant by Linus somewhere on that...
https://web.archive.org/web/
Hi, Yes, I have seen this "rant" but its nonsense of course. My small
rant. Just because it wasn't added, doesn't mean it was the proper to
keep it out for what many would consider a natural design element for
copying/moving files around. As with most things, it could of been made
optional
Hi Mark,
Sorry, I wasn't clear. I don't know *nix OSes much, but under Windows
(NTFS), we have 3 file time stamps for each file (Creation, Last Read and
Last Write). I think it would practical only to consider the last write
time.
I don't see any technical reason for not having it other the
Hi, yes it can be awkward when different systems make different choices about
which feature they want to use as the indicator for what they really want to
look at. For git the sha1 object id (oid) is what tells you that it has
changed. Its unfortunate that the 'timestamp' concept is used elsewhe
Good point about time zones differences. There were certainly bias design
issues. In our update server, it would take the bias into account to strive
for persistency. It seriously helps with tech support when eyeballing file
sizes and times with customers. Your right, it would be an option and
On 2017-06-05, at 4:39 PM, Philip Oakley wrote:
> Hi, yes it can be awkward when different systems make different choices about
> which feature they want to use as the indicator for what they really want to
> look at. For git the sha1 object id (oid) is what tells you that it has
> changed. I
Q. What is GIT?
GIT is a distributed version control system and source code management
(SCM) system with an emphasis to handle small and large projects with speed
and efficiency.
--
Q. What is a repository in GIT?
A repository contains a directory named .git, where g
13 matches
Mail list logo
