On Wed, 13 Mar 2024, Paul M Foster wrote:
Folks:
I have a /home/paulf/stow directory with contains subdirectories for each
of the packages whose dotfiles I want to manage, like:
/home/paulf/stow/alacritty
In each subdirectory, I have all the config files for that packages, under
git
files for that packages, under
git management. This means that the directory will look like this:
/home/paulf/stow/alacritty/.git
/home/paulf/stow/alacritty/.config/alacritty/alacritty.yml
This works well with stow (configs are now symlinks in $HOME).
I'd like to copy all of this to a git repo
On Wed, 13 Mar 2024, Paul M Foster wrote:
Folks:
I have a /home/paulf/stow directory with contains subdirectories for each
of the packages whose dotfiles I want to manage, like:
/home/paulf/stow/alacritty
In each subdirectory, I have all the config files for that packages, under
git
;
> > /home/paulf/stow/alacritty
> >
> > In each subdirectory, I have all the config files for that packages, under
> > git management. This means that the directory will look like this:
> >
> > /home/paulf/stow/alacritty/.git
> > /home/paulf/stow/alacritty/
On 3/13/24 16:04, Paul M Foster wrote:
Folks:
I have a /home/paulf/stow directory with contains subdirectories for each
of the packages whose dotfiles I want to manage, like:
/home/paulf/stow/alacritty
In each subdirectory, I have all the config files for that packages, under
git management
Folks:
I have a /home/paulf/stow directory with contains subdirectories for each
of the packages whose dotfiles I want to manage, like:
/home/paulf/stow/alacritty
In each subdirectory, I have all the config files for that packages, under
git management. This means that the directory will look
On 10/7/23 01:51, to...@tuxteam.de wrote:
On Fri, Oct 06, 2023 at 01:44:34PM -0700, Mike Castle wrote:
Something I played with recently was
https://packages.debian.org/stable/vcs/git-filter-repo
Yes, it does work. My typical use case is when someone has put a
password in the repo you don't
On Fri, Oct 06, 2023 at 01:44:34PM -0700, Mike Castle wrote:
> Something I played with recently was
> https://packages.debian.org/stable/vcs/git-filter-repo
Yes, it does work. My typical use case is when someone has put a
password in the repo you don't even want to have in the history.
B
Something I played with recently was
https://packages.debian.org/stable/vcs/git-filter-repo
But you definitely want to run tests on real data before you decide
that deleting old data saves your anything, particularly with respect
to time.
If git is so efficient at storing this kind of data
>> `git gc` does delete the old data (if it's not reachable any more).
> And it is very expensive. My point exactly.
It's fairly expensive indeed, but it's usually an operation that is not
very time-sensitive: it can usually be delayed to a convenient time, and
you can run it inf
Stefan Monnier (12023-10-06):
> `git gc` does delete the old data (if it's not reachable any more).
And it is very expensive. My point exactly.
> BTW, if you want to (ab)use a Git repository to do backups, you should
> definitely look at `bup`.
Thanks, it might be exactly what I a
> Have you tried? The very principle of Git makes it necessary, to remove
> or update old data, to rewrite the whole subsequent history.
> Furthermore, it is done by creating a new branch, the original data is
> not actually deleted.
`git gc` does delete the old data (if it's not r
john doe (12023-10-06):
> Please elaborate on why Git is so bad at removing data from a single
> repository?
Have you tried? The very principle of Git makes it necessary, to remove
or update old data, to rewrite the whole subsequent history.
Furthermore, it is done by creating a new
On 10/6/23 13:26, Nicolas George wrote:
john doe (12023-10-06):
I do not understand why you would want multiple repos, to me this looks
like this would fit the bill for a Git branching workflow.
Please elaborate. How do you work around the fact that Git is terrible
at removing data
Max Nikulin (12023-10-06):
> I have no idea if it is possible to do it in place, but "git clone" and "git
> fetch" have the --depth option. So you can specify how many last commits you
> would like to have in the cloned repository. Using "git rebase
I know
john doe (12023-10-06):
> I do not understand why you would want multiple repos, to me this looks
> like this would fit the bill for a Git branching workflow.
Please elaborate. How do you work around the fact that Git is terrible
at removing data with a single repository?
Regards,
--
N
On 10/6/23 11:14, Nicolas George wrote:
Hi.
There is a project I have that requires some scripting, but I am
wondering if somebody already did something similar and there is a
package that I can just apt-get install.
The idea is to use Git to store backups of text files that change rather
On 06/10/2023 16:14, Nicolas George wrote:
Unfortunately, Git is very bad at removing old data
I have no idea if it is possible to do it in place, but "git clone" and
"git fetch" have the --depth option. So you can specify how many last
commits you would like to have in t
Hi.
There is a project I have that requires some scripting, but I am
wondering if somebody already did something similar and there is a
package that I can just apt-get install.
The idea is to use Git to store backups of text files that change rather
rarely or not a lot, because Git is very
On Sat, Sep 09, 2023 at 04:31:38PM -0400, David Mehler wrote:
> Hello,
>
> I'm trying to set up a git server on Debian 12, served by Nginx via
> https. I used this as a debian-specific starter though I have done
> this in the past using a FreeBSD and Apache type setup:
>
>
er wrote:
>> I'm trying to set up a git server on Debian 12, served by Nginx via
>> https. I used this as a debian-specific starter though I have done
>> this in the past using a FreeBSD and Apache type setup:
>>
>> https://esc.sh/blog/setting-up-a-git-http-server-
Hello,
I'm trying to set up a git server on Debian 12, served by Nginx via
https. I used this as a debian-specific starter though I have done
this in the past using a FreeBSD and Apache type setup:
https://esc.sh/blog/setting-up-a-git-http-server-with-nginx/
The client is a windows 10 client
On Fri, 2023-08-25 at 22:36 +, Russell L. Harris wrote:
> If pushing from PRODUCTION is more reliable or less trouble-prone than
> pulling from BACKUP, kindly explain to me, and I shall change.
Another consideration is that to pull from PRODUCTION requires it to be
running a service (e.g.
On Sat, Aug 26, 2023 at 08:10:20AM -0300, Eduardo M KALINOWSKI wrote:
[...]
> The reliability should be the same, but you cannot push to a non-bare
> repository. At least not in the standard configuration, but git being git
> I'm sure there's a way to override that.
Actually, if
change.
The reliability should be the same, but you cannot push to a non-bare
repository. At least not in the standard configuration, but git being
git I'm sure there's a way to override that.
--
Parents often talk about the younger generation as if they didn't have
much of anything to do
s context
> > >
> > > You can make a repo bare by editing it's config file (.git/config) to
> > > have 'bare = true' instead of 'bare = false' under the '[core]'
> > >
> >
> > Generaly, the '.git' extension symbolises a bare repository!
>
> The o
n described is perfectly suited to this
scenario. Arrange it so that when you run "git push" in your working
repository, it sends your commits to the central repository. (There
may be a prompt for your password or your passphrase, depending on how
you've configured ssh to the remote syst
On Fri, Aug 25, 2023 at 09:54:02AM +0200, Loris Bennett wrote:
Does a bare remote to which you simply push not already provide you with
an adequate backup? One you have made a number of commits, you can just
push them to the remote.
I am old and my fingers sometimes strike the wrong keys.
On Fri, 2023-08-25 at 19:47 +0200, john doe wrote:
> On 8/25/23 13:44, Tixy wrote:
> > On Fri, 2023-08-25 at 10:47 +0200, to...@tuxteam.de wrote:
> > > Yes, I think a bare remote is the way to go in this context
> >
> > You can make a repo bare by editing
On 8/25/23 13:44, Tixy wrote:
On Fri, 2023-08-25 at 10:47 +0200, to...@tuxteam.de wrote:
Yes, I think a bare remote is the way to go in this context
You can make a repo bare by editing it's config file (.git/config) to
have 'bare = true' instead of 'bare = false' under the '[core
On Fri, 2023-08-25 at 10:47 +0200, to...@tuxteam.de wrote:
> Yes, I think a bare remote is the way to go in this context
You can make a repo bare by editing it's config file (.git/config) to
have 'bare = true' instead of 'bare = false' under the '[core]'
section. I do this after copying the .
On 8/25/23 09:04, Russell L. Harris wrote:
On Fri, Aug 25, 2023 at 07:24:59AM +0100, Tixy wrote:
On Thu, 2023-08-24 at 22:24 +, Russell L. Harris wrote:
I'm also a bit confused about doing it this way. The usual workflow
with git is to 'push' to the remote repository, which is in fact what
On Fri, Aug 25, 2023 at 09:54:02AM +0200, Loris Bennett wrote:
[...]
> Does a bare remote to which you simply push not already provide you with
> an adequate backup? One you have made a number of commits, you can just
> push them to the remote.
Yes, I think a bare remote is the way to go in
"Russell L. Harris" writes:
> On Fri, Aug 25, 2023 at 07:24:59AM +0100, Tixy wrote:
>>On Thu, 2023-08-24 at 22:24 +, Russell L. Harris wrote:
>>> #!/bin/bash
>>> # post-commit
>>> # 2023.08.24 2200gmt
>>>
>>> ssh backup &qu
On Fri, Aug 25, 2023 at 07:24:59AM +0100, Tixy wrote:
On Thu, 2023-08-24 at 22:24 +, Russell L. Harris wrote:
#!/bin/bash
# post-commit
# 2023.08.24 2200gmt
ssh backup "git pull"
exit 0
You could omit the 'exit 0' so it returns the error code from the ssh
command, that way
On Thu, 2023-08-24 at 22:24 +, Russell L. Harris wrote:
> #!/bin/bash
> # post-commit
> # 2023.08.24 2200gmt
>
> ssh backup "git pull"
> exit 0
>
You could omit the 'exit 0' so it returns the error code from the ssh
command, that way you'll get some feedbac
On Tue, Aug 22, 2023 at 12:59:18AM -0400, Karl Vogel wrote:
me% cat try
#!/bin/sh
export PATH=/usr/local/bin:/bin:/usr/bin
ssh -q -c aes128-...@openssh.com -i $HOME/.ssh/bkup_ed25519 \
bkup "logger -t autopull git pull whatever"
exit 0
I a
no fuss at all.
Almost every version control system (besides legacy ones, e.g. RCS) is
designed to combine changes from multiple working copies evolving in
parallel.
Of course, git facilities allows to synchronize multiple repositories
with minimal risk to loose changes committed to any copy
On Tue, 22 Aug 2023 19:27:57 +
Michael Kjörling <2695bd53d...@ewoof.net> wrote:
> On 22 Aug 2023 14:33 -0400, from cele...@gmail.com (Celejar):
> >> Git tends to be very rsync-friendly.
> >
> > I do something similar - I use syncthing to automatically keep t
On 22 Aug 2023 14:33 -0400, from cele...@gmail.com (Celejar):
>> Git tends to be very rsync-friendly.
>
> I do something similar - I use syncthing to automatically keep the git
> repositories on two of my machines in sync. rsync may be better, but
> syncthing has more or less w
On Tue, 22 Aug 2023 16:31:58 +0200
wrote:
> On Tue, Aug 22, 2023 at 09:16:47AM -0500, John Hasler wrote:
> > Christoph writes:
> > > I have almost the same setup and use local git repositories. Instead
> > > of syncing them by the git tools I use rsync to update
o, which the OP would call
BACKUP, is on a headerless machine, so I used gitolite there, and git
administration is all over ssh. That gets backed up daily using amanda.
I have two laptops, a desktop and a plethora of other machines. Each of
those has such repos as are appropriate to that machine. A
On Tue, Aug 22, 2023 at 03:00:33AM +, Russell L. Harris wrote:
> My needs are simple. I need two git repositories.
>
> The first is my work space, into which periodically I commit the
> article on which I am working.
>
> The second repository is my backup; it resides
On 2023-08-22 03:00 +, Russell L. Harris wrote:
> After much searching and reading, I have not discovered how to set up
> a pair of git repositories to work together.
>
> I write articles for publication. I typically spend anywhere from
> several hours to many days
On Tue, Aug 22, 2023 at 09:16:47AM -0500, John Hasler wrote:
> Christoph writes:
> > I have almost the same setup and use local git repositories. Instead
> > of syncing them by the git tools I use rsync to update the backup from
> > time to time. This is a dum
Christoph writes:
> I have almost the same setup and use local git repositories. Instead
> of syncing them by the git tools I use rsync to update the backup from
> time to time. This is a dumb method but it works.
This is what I do as well.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On 8/22/23 05:00, Russell L. Harris wrote:
After much searching and reading, I have not discovered how to set up
a pair of git repositories to work together.
This makes no sense, that is what Git is for! :)
In the past, I have found git to be a very good solution. But now I
am moving
Am Tue, Aug 22, 2023 at 03:00:33AM + schrieb Russell L. Harris:
Hello Russel,
I cannot answer your question directly but show what I am doing now.
> After much searching and reading, I have not discovered how to set up
> a pair of git repositories to work together.
>
> I wr
I'd set up a post-commit hook on the production system. Have it SSH to
your backup system and do a pull automatically whenever you commit a change.
I made an example project to try it:
me% mkdir example
me% cd example
me% git init
Test file:
me% date > testing
me% git add
After much searching and reading, I have not discovered how to set up
a pair of git repositories to work together.
I write articles for publication. I typically spend anywhere from
several hours to many days on each article. It is frustrating to work
for an hour or two on a paragraph or a page
Dear DataLad and git-annex users,
We started planning a first meeting for everyone interested in DataLad
and git-annex in the first half of 2024! If you find that as
exhilarating as we do, head over to https://t.co/7RjLHyWtnl
and help us shape the event.
Cheers,
--
Yaroslav O. Halchenko
Center
On Thu, May 11, 2023 at 07:05:21PM -0400, Stefan Monnier wrote:
> > git remote remove origin
> > # this re-adds it
> > git remote add origin
>
> Better go with
>
> git remote set-url origin
Right :)
Cheers
--
t
signature.asc
Description: PGP signature
> git remote remove origin
> # this re-adds it
> git remote add origin
Better go with
git remote set-url origin
-- Stefan
On 5/10/23 05:47, William Torrez Corea wrote:
Command:
git push master origin
I want upload my change to branch MAIN but when i want upload my change i
get the following error:
remote: Support for password authentication was removed on August 13, 2021.
remote: Please see
https
On 2023-05-10 05:49:19 +0100, Tim Woodall wrote:
> On Tue, 9 May 2023, William Torrez Corea wrote:
>
> > Command:
> >
> > git push master origin
> > >
>
> shouldn't that be git push origin master? Or even origin main?
Or in general, simp
On Tue, May 09, 2023 at 09:47:45PM -0600, William Torrez Corea wrote:
> Command:
>
> git push master origin
> >
>
> I want upload my change to branch MAIN but when i want upload my change i
> get the following error:
>
> remote: Support for password authentication
On Tue, May 09, 2023 at 09:47:45PM -0600, William Torrez Corea wrote:
> Command:
>
> git push master origin
> >
>
> I want upload my change to branch MAIN but when i want upload my change i
> get the following error:
>
> remote: Support for password authentication
On Tue, 9 May 2023, William Torrez Corea wrote:
Command:
git push master origin
shouldn't that be git push origin master? Or even origin main?
I want upload my change to branch MAIN but when i want upload my change i
get the following error:
remote: Support for password authentication
Command:
git push master origin
>
I want upload my change to branch MAIN but when i want upload my change i
get the following error:
remote: Support for password authentication was removed on August 13, 2021.
> remote: Please see
> https://docs.github.com/en/get-started/getting-started
Le lundi 03 avril 2023 à 10:24 +0200, Christophe Maquaire a écrit :
Bonjour de nouveau,
Bon, je m'en suis sorti, le nom de la branche git mentionnée dans le
thread est erroné
0.12.1rc1 => lire 0.12.1
Bonne journée
solution est proposée,
Mais je ne sais pas la mettre en oeuvre, en clair je ne sais pas
produire la commande git qui permet de cloner localement la bonne
version
les infos sont là:
https://lists.gnu.org/archive/html/mediagoblin-devel/2023-03/msg00013.html
Si une bonne âme maitrisant git
Peut-être que l'explication se trouve là
https://www.blog-nouvelles-technologies.fr/256050/github-etend-obligation-2fa-lundi-13-mars/
Le 14/03/2023 à 11:22, Basile Starynkevitch a écrit :
Bonjour à tous,
Je n'arrive plus à faire un git push vers github.com
Sur mon ordinateur portable
Bonjour Basile,
Il est important de lire les messages d'erreur qui sortent sur un
terminal, parce que sinon on perd son temps et éventuellement on fait
perdre le leur aux autres.
Basile Starynkevitch wrote on 14/03/2023 at
11:22:49+0100:
> Bonjour à tous,
>
> Je n'arrive plus à fai
Bonjour,
La réponse est dans le lien fourni:
remote: Support for password authentication was removed on August 13,
2021.
remote: Please see
https://docs.github.com/en/get-started/getting-started-with-git/about-remote-repositories#cloning-with-https-urls
for information on currently
Bonjour à tous,
Je n'arrive plus à faire un git push vers github.com
Sur mon ordinateur portable personnel (ACER Nitro 5, x86-64, Debian/Sid,
...)
guiseppe.x86_64 ~/RefPerSys 10:43 .0 % git push
Username for 'https://github.com': bas...@starynkevitch.net
Password for 'https://bas
On Sun, Mar 05, 2023 at 09:05:01AM +0100, john doe wrote:
> On 3/5/23 04:59, William Torrez Corea wrote:
> > I am working with remotes, when i want push to the remote with this command
>
> What CMD?
>
> > appear the following error:
> >
> > *git pus
On Sat, Mar 04, 2023 at 11:13:04PM -0500, Larry Martell wrote:
> On Sat, Mar 4, 2023 at 11:00 PM William Torrez Corea wrote:
>
> > I am working with remotes, when i want push to the remote with this
> > command appear the following error:
> >
> > *git push main mast
On 3/5/23 04:59, William Torrez Corea wrote:
I am working with remotes, when i want push to the remote with this command
What CMD?
appear the following error:
*git push main master*
This error looks to indicate that you are pushing to main and master
branches.
fatal: 'main' does
On Sat, Mar 04, 2023 at 09:59:29PM -0600, William Torrez Corea wrote:
> I am working with remotes, when i want push to the remote with this command
> appear the following error:
>
> *git push main master*
>
> fatal: 'main' does not appear to be a git repository
> > fa
On Sat, Mar 4, 2023 at 11:00 PM William Torrez Corea
wrote:
> I am working with remotes, when i want push to the remote with this
> command appear the following error:
>
> *git push main master*
>
> fatal: 'main' does not appear to be a git repository
>> fatal: Co
I am working with remotes, when i want push to the remote with this command
appear the following error:
*git push main master*
fatal: 'main' does not appear to be a git repository
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct acce
On Sat, 28 Jan 2023 at 03:56, Tixy wrote:
> On Fri, 2023-01-27 at 11:28 +, Brad Rogers wrote:
> > On Fri, 27 Jan 2023 11:36:12 +0100 "Sijmen J. Mulder"
> > wrote:
> > > I was surprised to find that the recent git vulnerability hasn't yet
> > &g
On Fri, 27 Jan 2023 16:56:31 +
Tixy wrote:
Hello Tixy,
>Does it? It links to a bug which says it's been fixed in sid. And the
To be fair, the page lists more than just that; It lists the status
for everything from Buster to Sid.
Add that to the info given by Greg Wooledge (thank you
On Fri, Jan 27, 2023 at 04:56:31PM +, Tixy wrote:
> On Fri, 2023-01-27 at 11:28 +, Brad Rogers wrote:
> > The security-tracker CVE page you cited has links to all the
> > information you requested.
>
> Does it? It links to a bug which says it's been fixed in sid. And the
> PTS shows it
On Fri, 2023-01-27 at 11:28 +, Brad Rogers wrote:
> On Fri, 27 Jan 2023 11:36:12 +0100
> "Sijmen J. Mulder" wrote:
>
> Hello Sijmen,
>
> The security-tracker CVE page you cited has links to all the
> information you requested.
>
Does it? It links to a bug which says it's been fixed in
On Fri, 27 Jan 2023 11:36:12 +0100
"Sijmen J. Mulder" wrote:
Hello Sijmen,
The security-tracker CVE page you cited has links to all the
information you requested.
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately
On Fri, 27 Jan 2023 at 21:36, Sijmen J. Mulder wrote:
>
> Hi all,
>
> I was surprised to find that the recent git vulnerability hasn't yet
> been addressed in Bullseye:
Hi. More info here:
https://www.debian.org/security/faq
and here:
https://security-tracker.debian.org/t
Hi all,
I was surprised to find that the recent git vulnerability hasn't yet
been addressed in Bullseye:
https://security-tracker.debian.org/tracker/CVE-2022-41903
My question isn't about the situation of this package per se but about
the process. I found this diagram:
https://wiki.debian.org
Hellow Ash,
Ash Joubert writes:
> On 07/06/2022 20:01, 황병희 wrote:
>> ===> Correction: git pull origin karma
>
> This means fetch commits from the "karma" branch/tag on repository
> "origin" and incorporate them into the current local branch with a
&g
On Wed, Jun 08, 2022 at 04:38:22PM +1200, Ash Joubert wrote:
> On 08/06/2022 16:25, to...@tuxteam.de wrote:
> > Just... what does "Pro Git" mean?
>
> Pro Git is the name of a well-known book on git that is also available free
> in HTML and PDF formats [...]
Oh, I se
On 08/06/2022 16:25, to...@tuxteam.de wrote:
Just... what does "Pro Git" mean?
Pro Git is the name of a well-known book on git that is also available
free in HTML and PDF formats. In addition to the basics that can be
found in the git man pages, it contains best-practices and b
On Wed, Jun 08, 2022 at 10:31:03AM +1200, Ash Joubert wrote:
> On 07/06/2022 20:01, 황병희 wrote:
> > ===> Correction: git pull origin karma
>
> This means fetch commits from the "karma" branch/tag on repository "origin"
> and incorporate them into the cu
On 07/06/2022 20:01, 황병희 wrote:
===> Correction: git pull origin karma
This means fetch commits from the "karma" branch/tag on repository
"origin" and incorporate them into the current local branch with a merge
or rebase. See the man page for git-pull for a detailed
황병희 writes:
> ...
> - git pull -b karma
Ack! my mistake!!! I am very sorry!!!
===> Correction: git pull origin karma
Sorry again john and IL!
Sincerely, Linux fan Byung-Hee
--
^고맙습니다 _地平天成_ 감사합니다_^))//
>
> According to (1), that would be the ''-b, -w, --ignore-space-at-eol, and
> --ignore-cr-at-eol' option and the 'repository'.
>
>
This is a "git diff" option, not "git pull" option AFAIK
On 6/7/2022 6:26 AM, 황병희 wrote:
Hellow Debian,
For days, i have been working with git.
And today i have very simple question.
Because it is very confused...
I need somebody's clearing.
What is different both commands:
- git pull
- git pull -b karma
According to (1), that would be the ''-b
Hi
> - git pull
>
Fetch data from remote repository and merge local branch or rebase it on
top of new commits.
> - git pull -b karma
>
I do know what "-b" is.
Documentation also doesn't: https://git-scm.com/docs/git-pull
$ git pull -b asd
error: unknown switch `b'
The
Hellow Debian,
For days, i have been working with git.
And today i have very simple question.
Because it is very confused...
I need somebody's clearing.
What is different both commands:
- git pull
- git pull -b karma
Thanks in advance!
Sincerely, Linux fan Byung-Hee
--
^고맙습니다 _地平天成_ 감사합니다_^))//
El 15/5/22 a las 04:43, Camaleón escribió:
El 2022-05-14 a las 19:39 -0400, Roberto C. Sánchez escribió:
On Sat, May 14, 2022 at 04:32:04PM -0300, JavierDebian wrote:
Buenas tardes.
Preguntonta:
¿Qué tan seguro es el repositorio git éste?
https://salsa.debian.org/public
Depende en tu
El 2022-05-14 a las 19:39 -0400, Roberto C. Sánchez escribió:
> On Sat, May 14, 2022 at 04:32:04PM -0300, JavierDebian wrote:
> > Buenas tardes.
> >
> > Preguntonta:
> >
> > ¿Qué tan seguro es el repositorio git éste?
> >
> > https://salsa.deb
On Sat, May 14, 2022 at 04:32:04PM -0300, JavierDebian wrote:
> Buenas tardes.
>
> Preguntonta:
>
> ¿Qué tan seguro es el repositorio git éste?
>
> https://salsa.debian.org/public
>
Depende en tu modelo de seguridad. Si hay un paquete y te hace falta
alguna versión q
El principal de debian hasta donde yo sé...
El 14 may. 2022 21:32, JavierDebian escribió:
Buenas tardes.
Preguntonta:
¿Qué tan seguro es el repositorio git éste?
https://salsa.debian.org/public
Gracias.
JAP
Buenas tardes.
Preguntonta:
¿Qué tan seguro es el repositorio git éste?
https://salsa.debian.org/public
Gracias.
JAP
On Fri, Nov 26, 2021, 7:57 AM Harald Dunkel wrote:
> Hi folks,
>
> trying to build git 2.34.0-1 for bullseye I get 2 segfaults (see #991214).
> Apparently they pop up during the built-in tests, so I wonder if this is a
> FTBFS? If this is nothing to worry about, how comes that
Hi folks,
trying to build git 2.34.0-1 for bullseye I get 2 segfaults (see #991214).
Apparently they pop up during the built-in tests, so I wonder if this is a
FTBFS? If this is nothing to worry about, how comes that these segfaults
are not caught like the others?
Regards
Harri
Le 12/07/21 à 22:29, Arnaud Vandyck a écrit :
> Peut-être avec —ignore-paths
> https://stackoverflow.com/questions/7668752/git-svn-ignore-paths
Excellente suggestion, merci, ça fait ce que je voulais :-)
Et toutes mes confuses… j'aurais pu trouver ça tout seul en fouillant mieux la
d
Peut-être avec —ignore-paths
https://stackoverflow.com/questions/7668752/git-svn-ignore-paths
Mais je n’ai jamais essayé.
-- Arnaud sur son iPhone
> Le 12 juil. 2021 à 18:07, Daniel Caillibaud a écrit :
>
> Le 09/07/21 à 20:45, Arnaud Vandyck a écrit :
>> Peut-être en
Le 09/07/21 à 20:45, Arnaud Vandyck a écrit :
> Peut-être en filtrant le svn comme dans ce projet?
>
> https://stackoverflow.com/questions/15535334/filter-a-lot-of-sensitive-code-from-an-svn-repository
>
> Les gros fichiers obsoletes seraient exclus du dépôt.
Oui, c'est ce que j'envisageais
aud a écrit :
> Salut,
>
> Une question git (qui n'a donc rien à voir avec debian).
>
> - J'ai un dépôt svn d'un très vieux projet, encore actif, avec des
> utilisateurs habitués à svn.
>
> - J'aimerais permettre à ceux qui utilisent git couramment de pouvoir le
> fai
Salut,
Une question git (qui n'a donc rien à voir avec debian).
- J'ai un dépôt svn d'un très vieux projet, encore actif, avec des utilisateurs
habitués à svn.
- J'aimerais permettre à ceux qui utilisent git couramment de pouvoir le faire
sur ce projet
=> git-svn [1] permet de faire
1 - 100 of 507 matches
Mail list logo
