# git annex initremote cloud type=S3 encryption=2512E3C7 Next, create the S3 remote, and describe it. Once you haveĪ gpg key, run `gpg -list-secret-keys` to look up its key id, something To encrypt everything stored in S3, for your privacy. Now, create a gpg key, if you don't already have one. This way you can set up a remote using say,Īmazon S3, and use git-annex to transfer files into the cloud. This is a public inbox, see mirroring instructionsįor how to clone and mirror all data and code used for this inbox Īs well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).Git-annex extends git's usual remotes with some ], thatĪre not git repositories. * If your mail client supports setting the In-Reply-To headerīe sure your reply has a Subject: header at the top and a blank line * Reply using the -to, -cc, and -in-reply-to * Save the following mbox file, import it into your mail client,Īvoid top-posting and favor interleaved quoting: You may reply publicly to this message via plain-text email 18:08 Philippe Waroquiers 4:55 ` Simon Marchi Thread overview: 3+ messages / expand mbox.gz Atom feed top Would it be possible to split the changes that remove the trailing Thanks, this is a nice cleanup, this LGTM. > (linux_xfer_osdata_isockets): Likewise. > (linux_xfer_osdata_processgroups): Likewise. > (linux_xfer_osdata_processes): Likewise. Only keep the code that adds data in BUFFER. > (linux_xfer_osdata_cpus): Remove args READBUF, OFFSET, LEN. > (linux_common_xfer_osdata): Use common_getter for the list of types. > (linux_xfer_osdata_info_os_types): New function. > Change all elements in the initializer. > Add LONGEST len_avail and struct buffer buffer. > (struct osdata_type): Change getter to take_snapshot. > * nat/linux-osdata.c : Removed various trailing spaces. > So, git diff -w helps to look only at the relevant differences. > Note: git diff/git format-patch shows a lot of differences only due > only build the xml data in a struct buffer. > anymore any logic related to the partial transfer of data: they now > Thanks to this, all the linux_xfer_osdata_* do not have > of the struct osdata_type instead of being a static var of each The buffer for a specific annex is now a member > of the 'static struct buffer' is factorized in a new function > a non neglectible amount of duplicated code, the setup and usage > Also, because this bug was replicated in all functions, and there was > the 'static char *buf' and accessing the struct buffer memory where > from a local var to another local var, so the fix consists in dropping > I see no reason why the ownership of the memory has to be transferred > to their 'static char *buf' local var, but then call buffer_free > transfer the ownership of their 'static struct buffer' memory > The leaks are created because the linux_xfer_osdata_* functions > unsigned long, unsigned long) (linux-osdata.c:370) > =10592= by 0x5263DF: linux_xfer_osdata_processes(unsigned char*, > =10592= by 0x408BC3: buffer_grow(buffer*, char const*, unsigned > =10592= 65,536 bytes in 1 blocks are definitely lost in loss record > A typical leak (this one is of gdb.base/info-os) is: > Valgrind reports leaks in all linux osdata annex transfers of Simon Marchi public inbox for help / color / mirror / Atom feed From: Simon Marchi Ĭc: Re: Fix leaks in all the linux osdata annex transfers + code factorization.ĭate: Tue, 04:55:00 -0000 Re: Fix leaks in all the linux osdata annex transfers + code factorization.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |